This is the mail archive of the
mailing list for the Archer project.
Re: gdb side of improved linker-debugger interface
Jan Kratochvil wrote:
> On Wed, 08 Jun 2011 13:00:44 +0200, Gary Benson wrote:
> > > the testcase from:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=179072#c13
> > It actually doesn't fail on standard F14 gdb:
> Please do:
> # prelink -u /lib64/libpthread-2.13.so
> $ gdb ./testload
> GNU gdb (GDB) Fedora (7.2-51.fc14)
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> For bug reporting instructions, please see:
> Reading symbols from /home/jkratoch/t/rh179072-tests/testload...done.
> (gdb) r
> Starting program: /home/jkratoch/t/rh179072-tests/testload
> [Thread debugging using libthread_db enabled]
> Cannot find new threads: generic error
> (gdb) _
Ah, after unprelinking I get that failure with F14 gdb. But, it works
nicely with the new stuff:
$ ../build/gdb/gdb -args ../../glibc/install/lib/ld-2.13.90.so ./testload
GNU gdb (GDB) 188.8.131.5210510-cvs
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /home/gary/work/glibc/install/lib/ld-2.13.90.so...done.
Starting program: /home/gary/work/glibc/install/lib/ld-2.13.90.so ./testload
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff762a700 (LWP 6969)]
[Thread 0x7ffff762a700 (LWP 6969) exited]
[Inferior 1 (process 6966) exited normally]
I'm glad I have this reproduced now, it's IMO a much more compelling
argument for the fix than the somewhat arbitrary testcase the bug was
originally filed with.