Would this allow what I was asking you about before with FCEUX type table generation of ROM access execute vs data for help in disasm? Just curious if that may be down the road, I know you're busy with 21fx right now.
- assist a full-fledged disassembler (though it can't help with non-executed areas; that would have to fall back on heuristics)
- identify code vs execution areas
- find unused portions of WRAM and SRAM for use with hacks
etc.
I compiled the BSNES sources on Ubuntu today, but I can't find the debugger anywhere. Is there a flag I need to set when building BSNES in order to get the debugger included?
mic_ wrote:I compiled the BSNES sources on Ubuntu today, but I can't find the debugger anywhere. Is there a flag I need to set when building BSNES in order to get the debugger included?
Yeah, it's in one of the main header files, can't remember the name.
I've got another idea for an improvement to the debugger: it'd be nice if bsnes could read the SYM files generated by wlalink, so that I could set breakpoints on symbols and get label names when I step/trace my code. You can generate a SYM file by adding a capital S to your link switches (IIRC).. they're just text files with address/name pairs in plain text.