Thanks for the indirect plug, Uz! I'd love to do something similar to what I'm doing in NESICIDE [www.nesicide.com] for VICE. A screenshot of mixed-mode debugging a game written in C for NES [rather old but still mostly pertinent]: http://i.imgur.com/gdhNF.png. If you pay careful attention to the mixed-mode window, the breakpoints, and the current-execution pointer, you'll see that NESICIDE is able to break on C language code constructs like for loops either at the initiator or iterator portion of the code [alternatively you can set breakpoints in the Assembly Browser at any assembly instruction]. It can also step-over or step-into functions. I'm working on step-out still. Symbols can be dragged from C or assembly source files into the Symbol Watch window (which now also auto-populates sub-tabs with declared symbols in the NES RAM areas). The Code Profiler on the left is also something of a work-in-progress to be able to get min/max/avg cycle counts of functions. I'm also interested in any improvements you [Uz] come out with in the dbginfo stuff! ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Mar 15 21:01:54 2012
This archive was generated by hypermail 2.1.8 : 2012-03-15 21:01:56 CET
