FS#14481 - [glibc-2.9-5 (testing)] breaks gdb
Attached to Project:
Arch Linux
Opened by Georg Grabler (STiAT) - Monday, 27 April 2009, 23:23 GMT
Last edited by Allan McRae (Allan) - Wednesday, 29 April 2009, 10:55 GMT
Opened by Georg Grabler (STiAT) - Monday, 27 April 2009, 23:23 GMT
Last edited by Allan McRae (Allan) - Wednesday, 29 April 2009, 10:55 GMT
|
Details
Description:
The new version of gdb in testing breaks gdb. It will throw the error find_new_threads_callback: cannot get thread info: generic error and not start the application at all. Additional info: * glibc-2.9-5 Steps to reproduce: Install glibc-2.9-5 and run in example $ gdb qgit (gdb) r This will throw the errors, the application will not appear, no debugging will be possible. I downgraded to glibc-2.9-4 (binutils-2.19.1-1) - and it works properly again. The gdb developers meant it's about stripping symbols out of libpthread - i can not confirm this by 100 %, but it pointed me in the right direction (glibc). |
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 29 April 2009, 10:55 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.9-7. Really...
Wednesday, 29 April 2009, 10:55 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.9-7. Really...
Can test for example with /usr/bin/chattr that are part of [core]
sed -i 's#static \(bool __nptl_initial_report_events\)#\1#' nptl/init.c
Allan wait a minute...
there are a commit from truck with not remove "static", just add __attributed_used__, i will test it with 2.9_branch...
http://cvs.fedora.redhat.com/viewvc/devel/glibc/thread_db.patch?view=co
Thanks for helping to track this down so fast djgera, you did a great job finding all this information.
Thanks to Allan as well for the fast response.
patch -Np1 -i ${srcdir}/glibc-patches/glibc-2.9-libhread_db.patch
should be
patch -Np1 -i ${srcdir}/glibc-patches/glibc-2.9-libthread_db.patch || return 1
-> libthread not libhread (return 1 to recognize when it fails to patch).
Same error as before ;-)
Thanks anyway for being that responsive.
// G | STi