Page 2 of 2
Posted: Sun Dec 06, 2009 1:25 pm
by MottZilla
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.
Posted: Sun Dec 06, 2009 1:58 pm
by Near
Yes, usage.bin can be directly used to:
- 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.
Posted: Mon May 17, 2010 4:42 am
by mic_
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?
Posted: Mon May 17, 2010 5:44 am
by MatthewCallis
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.
Posted: Mon May 17, 2010 6:39 am
by mic_
Adding -DDEBUGGER to the flags in the makefile did the trick.
Posted: Mon Jan 03, 2011 8:25 am
by mic_
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.
Posted: Tue Jan 11, 2011 1:14 am
by magno
Is bsnes debugger version still on progress? Or was it dropped?
I can't see the binaries anymore on byuu website...
Posted: Thu Jan 13, 2011 4:01 pm
by Near
It needs GTK+ for the hex editor widget, but it is otherwise there and working.
Posted: Fri Jan 14, 2011 2:43 am
by magno
byuu wrote:It needs GTK+ for the hex editor widget, but it is otherwise there and working.
Those are great news for me!
I thought debugging wasn't anymore on windows version as you said in your webpage:
Lastly, the debugger is still Linux-only[...]
Posted: Fri Jan 14, 2011 12:54 pm
by tepples
Unless "works on Windows" means "feel free to install Ubuntu in VirtualBox on Windows".
Posted: Fri Jan 14, 2011 2:03 pm
by magno
So that means there is no debugging in the windows binaries anymore, doesn't it?
If so, could I compile the source code with -debugger option in Visual C or GCC for Windows?