On Tue, 21 Jun 2005 richbon-lists4800@xxxxxxxxxxxxxx wrote:
>
> Stella 2.0 alpha is very VERY cool. This is already coming in quite
> handy.
That's good to hear. I was hoping someone besides me thought it would
be useful.
One thing to be aware of: the version you have probably has a couple of
bugs that affect the disassembly. Symptoms are incorrect hex bytes in the
disassembly, and incorrect disassembly of zeropage,x instructions.. but
these are fixed in the latest CVS.
> One question - the docs say it can import symbol files, but I don't see
> any way to make use of them within the debugger, even in a limited way.
> Is it able to make any use of the symbol file at this point, or is
> that still in the works?
Try "loadsym filename". You should get "loaded filename OK" if it works,
or "unable to load filename" if not.
Also, try renaming the symbol file so it has the same name as the
cartridge, only with .sym on the end. Assuming that wasn't something
that I added after the alpha release, Stella should load the symbol
file automatically (though it won't tell you so).
Once the symbols are loaded, they should show up in the disassembly. Also
you should be able to refer to them in commands: "break mainLoop" if
you have a label called mainLoop, for instance.
If at this point you still can't get it to work, it's possible we released
a buggy alpha binary. Wait a few days, we'll eventually put out an Aplha
2 release. The symbol handling has undergone some major surgery in the
current CVS version (partly to avoid memory leaks, partly to fix a couple
of bugs).
I'm about to add a way to define symbols from within the debugger, and
save them into a new symbol file. Hopefully this will be useful for
the guys who disassemble commercial games (hi, Dennis!)
--
B.
Archives (includes files) at http://www.biglist.com/lists/stella/archives/
Unsub & more at http://stella.biglist.com
