Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Oliver Schmidt <ol.sc@web.de>
Newsgroups: comp.sys.apple2.programmer
Subject: Re: Generic question about Apple2 / cc65 debugging
Date: Fri, 11 Aug 2023 18:50:53 -0000 (UTC)
Message-ID: <ub5vud$6uso$1@solani.org>
References: <20230811201326.30841582@laptop-sigfox>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 11 Aug 2023 18:50:53 -0000 (UTC)
Injection-Info: solani.org; logging-data="228248"; mail-complaints-to="abuse@news.solani.org"
User-Agent: NewsTap/5.5 (iPhone/iPod Touch)
Cancel-Lock: sha1:WFUK+GOgQuSzgcVVn9ElVbuOu8U= sha1:q7D1qJ2DJ6RLKCfMSzyaEUpQRbc=
X-User-ID: eJwNxskBwCAIBMCWJMC6loMc/Zdg5jWuEOQ2OMzHRzh2/xxW64lsbnp/1WyjJk1W4c5wAhVrPScvEa0=
Xref: csiph.com comp.sys.apple2.programmer:6067

Hi Colin,

> how does one debug cc65-generated code while sucking at
> assembly?

Certainly not the silver bullet you might be looking for, but what's there:

Build with options that generate additional files which allow you to relate
addresses you see in the monitor of an emulator to your source code.

1. Create a map file. It tells you where your functions are placed in
memory: --mapfile <file>

2. Create a listing file with source comments. It tells you which source
code line belongs to which offset: --listing <file> --add-source

So even when you don't understand assembly you can this way follow which
source code line is currently executed or set breakpoints on a source code
line.

Regards,
Oliver