Re: How to specify a new but non-default path of gdb in gcc?
- From: Paul Pluzhnikov <ppluzhnikov-nsp@xxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 07:00:29 -0700
"LaBird" <wlcheung1975@xxxxxxxxx> writes:
I have installed a new gdb (6.6) in my own (normal user) account,
under /home/username/gdb/. The system already has one older
version of gdb, but I'd like to try out the new one without removing
the old one. The installation is successful, but instead of "gcc -g ...",
what should I put in the command line when compiling a C program,
so that the debug information of the new gdb can be added instead
of the default old version?
You are confused: the way your program is compiled, and which
debugger you use to debug it, are completely independent [1].
The "debug info of the new gdb" (or any gdb) is certainly *not*
added to your executable.
You do not need to recompile your program to debug it with your
new debugger. Just do
~/gdb/gdb /path/to/executable
Cheers,
[1] Except older debugger may not understand debug format of the
newer gcc version.
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
.
- Follow-Ups:
- References:
- Prev by Date: Re: How to specify a new but non-default path of gdb in gcc?
- Next by Date: Re: New Linux kernel written in BASIC to be released in 5 days.
- Previous by thread: Re: How to specify a new but non-default path of gdb in gcc?
- Next by thread: Re: How to specify a new but non-default path of gdb in gcc?
- Index(es):
Relevant Pages
|
|
