Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2.programmer > #6067
| From | Oliver Schmidt <ol.sc@web.de> |
|---|---|
| Newsgroups | comp.sys.apple2.programmer |
| Subject | Re: Generic question about Apple2 / cc65 debugging |
| Date | 2023-08-11 18:50 +0000 |
| Message-ID | <ub5vud$6uso$1@solani.org> (permalink) |
| References | <20230811201326.30841582@laptop-sigfox> |
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
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
Generic question about Apple2 / cc65 debugging Colin Leroy-Mira <colin@colino.net> - 2023-08-11 20:13 +0200
Re: Generic question about Apple2 / cc65 debugging Oliver Schmidt <ol.sc@web.de> - 2023-08-11 18:50 +0000
Re: Generic question about Apple2 / cc65 debugging Colin Leroy-Mira <colin@colino.net> - 2023-08-12 15:12 +0200
Re: Generic question about Apple2 / cc65 debugging Oliver Schmidt <ol.sc@web.de> - 2023-08-12 20:39 +0000
csiph-web