Debugging GDB with GDB

Tim Combs tcombs@urbana.css.mot.com
Thu Nov 14 06:58:00 GMT 2002


The .gdbinit file uses "set prompt (top-gdb)" so you can differentiate 
between which gdb is running.  This works best on
the command line as you can readily see which gdb you are in.  Things
work the same as when you are debugging a program.  When you want to
stop use ctrl-c and you will see the top-level prompt and you can step
through gdb source.  When using the command line, I've always found it
helpful to open the source file I'm debugging to follow along.

Hope this helps
Tim

On Thu, Nov 14, 2002 at 03:13:07PM +0100, James Sampson wrote:
> Hello
> 
> GDB doesn't recognize a COFF file that I have made to a certain target - In 
> that respect I wish to see whats going on "inside" the GDB, so I'm using GDB 
> to debug itself - Only thing is, that I don't know how this is done.
> I'm using GDB 5.0 to debug GDB 5.2.1, but how do I break or step the GDB when 
> I have started the GDB being debugged? - The debugged GDB has control of the 
> console. Is there any way I can use another console for debugging, or is there 
> another way to do this?.
> 
> Cheers,
> 
> J.S.
> 



More information about the Gdb mailing list