Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Debugging a gdb source
@ 2004-03-09  5:48 Kotian, Deepak
  2004-03-09  6:49 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Kotian, Deepak @ 2004-03-09  5:48 UTC (permalink / raw)
  To: gdb

Hi ,

I am trying to debug gdb source on Linux using already installed
dedugger ddd or gdb.
The source code text does not seem to be in sync with the 
execution when we do step. How do I get it in sync, please
let me know. The -g option seems to be set in the Makefile.
Please let me know.

Thanks and Regards
Deepak



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Debugging a gdb source
  2004-03-09  5:48 Debugging a gdb source Kotian, Deepak
@ 2004-03-09  6:49 ` Eli Zaretskii
  2004-03-09  6:54   ` linker dies building GDB (ppc64) Manoj Iyer
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2004-03-09  6:49 UTC (permalink / raw)
  To: Kotian, Deepak; +Cc: gdb

> Date: Tue, 9 Mar 2004 11:23:25 +0530
> From: "Kotian, Deepak" <Deepak.Kotian@patni.com>
> 
> I am trying to debug gdb source on Linux using already installed
> dedugger ddd or gdb.
> The source code text does not seem to be in sync with the 
> execution when we do step. How do I get it in sync, please
> let me know. The -g option seems to be set in the Makefile.

Most probably, this happens because GDB is compiled with
optimizations.  I usually find this not to be much of a nuisance, I
just need to remember stepping a couple of times more until the line
I'm interested in stops being printed by GDB as the current line; then
I know that this line's code finished being executed, and the
variables whose values it modifies can be examined.

If you are annoyed by this, I suggest to rebuild GDB without
optimizations.  Caveat emptor: doing so might cause the problems you
are debugging to go away.  That is why I suggest to get used to
debugging the optimized code.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* linker dies building GDB (ppc64)
  2004-03-09  6:49 ` Eli Zaretskii
@ 2004-03-09  6:54   ` Manoj Iyer
  0 siblings, 0 replies; 3+ messages in thread
From: Manoj Iyer @ 2004-03-09  6:54 UTC (permalink / raw)
  To: gdb


Hi all,

I am trying to build the CVS version of GDB 6.0.  I am trying to build
it as a 64bit binary on a powerpc 64 machine. The linker (collect2) seg
faults trying to link tclsh. Has anyone seen this before??. Here is the
linker message when it died.

gcc  tclAppInit.o
-L/home/manjo/project/gdb/config.patch/gdb_test/src/tcl/unix -ltcl8.4 -ldl
-lieee -lm \
        -Wl,-rpath,/usr/local/lib -o tclsh
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld:
/home/manjo/project/gdb/config.patch/gdb_test/src/tcl/unix/libtcl8.4.a(tclUnixInit.o):
invalid string offset 7627628 >= 1139 for section `.strtab'
/usr/bin/ld:
/home/manjo/project/gdb/config.patch/gdb_test/src/tcl/unix/libtcl8.4.a(tclUnixInit.o):
invalid string offset 1946186851 >= 1139 for section `.strtab'
/home/manjo/project/gdb/config.patch/gdb_test/src/tcl/unix/libtcl8.4.a(tclUnixInit.o)(*ABS*+0x496e697453637269):
multiple definition of `no symbol'
make[2]: *** [tclsh] Error 1
make[2]: Leaving directory
`/home/manjo/project/gdb/config.patch/gdb_test/src/tcl/unix'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/manjo/project/gdb/config.patch/gdb_test/src/tcl'
make: *** [all-tcl] Error 2

Thanks
Manoj Iyer


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-03-09  6:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-09  5:48 Debugging a gdb source Kotian, Deepak
2004-03-09  6:49 ` Eli Zaretskii
2004-03-09  6:54   ` linker dies building GDB (ppc64) Manoj Iyer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox