huamichaelchen / virtualagc

Automatically exported from code.google.com/p/virtualagc
Other
0 stars 0 forks source link

Add support for gdb command line options #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Add support for gdb command line options will allow for better integration 
with 3rd party debug GUI's.

launching the emulator could take a binary directly as the default input 
instead of using the --core option in the current version.

It should be possible to launch the tool like:

yaAGC Colossu249.bin

to start debugging. And use an option like --nodebug to launch just the 
simulation without debugging.

Original issue reported on code.google.com by ohommes@gmail.com on 21 Dec 2008 at 4:52

GoogleCodeExporter commented 9 years ago
Added the support for the gdb command-line options. You can now use the yaAGC 
as the
debugger in Code::Blocks or KDbg. You don't need a special intercept script.

You can load a binary image and a core image as you would expect with a normal 
gdb
tool: yaAGC <ropes.bin> <core>

Other options that are support can be found in the help option of yaAGC (e.g. 
the
--command option to pass a commands file). I tried as much as possible to stay
backwards compatible. To do this the default mode is to debug (so you need a
--nodebug option to run just the simulator) and I do not support the real gdb 
--core
option since that needs to support the proprietary previous semantic. Other 
than that
most gdb options will work.

Original comment by ohommes@gmail.com on 26 Dec 2008 at 3:24