Re: gdb and dynamically loaded code

1996-12-05 Thread H.J. Lu
> > I guess ld-linux.so is a special case - we can provide it unstripped. > > Thanks > How about this patch? It should make everyone happy. BTW, I am using binutils 2.7.0.3. -- H.J. Lu ([EMAIL PROTECTED]) --- Index: linux/ld-so/Config.mk diff -c linux/ld-so/Config.mk:1.1.1.1 linux/ld-s

Re: gdb and dynamically loaded code

1996-12-05 Thread Bruce Perens
From: [EMAIL PROTECTED] (H.J. Lu) > How do you debug a stripped binary? Unless I am wrong, if you want > to debug ld-linux.so.1, you have to compile it with -g and don't strip > it. It doesn't cost much in disk space. I think he was making the point that the .dynsym section is present in "strippe

Re: gdb and dynamically loaded code

1996-12-05 Thread Bruce Perens
Note that I am stripping all executables on the base floppies (to get them to fit). This means if ld-linux.so has to be unstripped, simply changing the package won't be enough. You have to tell me to fix it in the install floppy set. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROT

Re: gdb and dynamically loaded code

1996-12-05 Thread David Engel
H.J. Lu writes: > > Douglas Bates writes: > > > I have version 4.16-2 of the gdb package installed. When I start gdb > > > I get the warnings > > > warning: Unable to find dynamic linker breakpoint function. > > > warning: GDB will be unable to debug shared library initializers > > > warning: a

gdb and dynamically loaded code

1996-12-03 Thread Douglas Bates
I have version 4.16-2 of the gdb package installed. When I start gdb I get the warnings warning: Unable to find dynamic linker breakpoint function. warning: GDB will be unable to debug shared library initializers warning: and track explicitly loaded dynamic code. It would be very helpful to me