On 8/24/2012 6:56 AM, Ullrich von Bassewitz wrote: > ----- Ursprüngliche Mitteilung ----- >> I ask myself if >> >> 1. one could take the assembly output and use the data from >> the mapfile to "fix" the assembly output, or >> >> 2. hack ld65 to produce the assembly output (or hack it, as above) >> >> so one has an assembly listing resembling the real memory layout. > > I think, the way to go is source level debugging. I'm using the listing feature very rarely myself. I'm not sure how that would help me dump a range of memory on a target machine, assuming I had done the math in the first place to know where that range of memory actually ended up after linking. I suppose that might be possible on an emulator+IDE, though - assuming the hardware I'm interfacing with were emulated (unlikely in my particular Apple II case). I find myself using the listing quite frequently when it comes to debugging... I guess it comes down to different modes of working that programmers are comfortable with. Spiro and I might gang up and contribute a post-link disassembly fixup project. ;-) - David ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Aug 24 16:07:24 2012
This archive was generated by hypermail 2.1.8 : 2012-08-24 16:07:27 CEST