This is the mail archive of the
mailing list for the GDB project.
Re: How do you use GDB to debug GDB
- To: Stephen Smith <ischis2 at home dot com>
- Subject: Re: How do you use GDB to debug GDB
- From: jtc at redback dot com (J.T. Conklin)
- Date: 19 Mar 2001 13:01:07 -0800
- Cc: GDB <gdb at sourceware dot cygnus dot com>
- References: <3AB66BE3.D45096D0@home.com>
- Reply-To: jtc at redback dot com
>>>>> "Stephen" == Stephen Smith <firstname.lastname@example.org> writes:
Stephen> I have a gdb debugger configured to for a remote target (host
Stephen> i686-pc-cygwin target=powerpc-motorola-elf). normally I run
Stephen> gdb as:
Stephen> powerpc-motorola-elf-gdb --command=C:/rti/bin/rtidbug.ini C:/examples/dll/main.exe
Stephen> Now I want to run the gdb against the above process.
On a UNIX system, you would first start a native GDB, and then use it
to run and debug the child GDB.
$ gdb /usr/local/bin/powerpc-motorola-elf-gdb
GDB is free software and you are ...
At this point, I typically install breakpoints where I think there the
problem lies. The .gdbinit file distributed with GDB sets breakpoints
and sets directory paths, etc.; thus creating an initial environment
that are likely to be useful debugging GDB.
Then run your child GDB.
(gdb) run --command=C:/rti/bin/rtidbug.ini C:/examples/dll/main.exe
I don't have experience with NT to know whether this will work there.