Bug#414606: closed by Aurelien Jarno <aurelien@aurel32.net> (Closing bugs fixed in unreleased version 2.4-1 of the glibc)
This report might save someone a headache, but the bug should probably
stay closed. You might want to make new libc6 conflict with old
versions of gdb...
With gdb 6.6 and libc6 2.5-2, it seems to be fixed, at least on x86.
libc6-dbg works fine too.
However, under x86 and amd64 the bug came back with lib6c and libc6-dbg,
versions 2.5-1 and 2.5-2. I see the problem with them when I use gdb
6.4.90-dfsg-1. I'm pretty sure I didn't see the problem with 2.5-0exp6
and that version of gdb.
When I combined libc6-dbg 2.5-2 and gdb 6.4.90-dfsg, I got the following
error. All other combinations that I tried have corrupt stack traces,
as before:
(gdb) run
Starting program: /home/sears/deadlock/d
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1210431808 (LWP 6407)]
Program received signal SIGINT, Interrupt.
[Switching to Thread -1210431808 (LWP 6407)]
0xb7ef2da9 in __lll_mutex_lock_wait () from /usr/lib/debug/libpthread.so.0
(gdb) where
#0 0xb7ef2da9 in __lll_mutex_lock_wait () from
/usr/lib/debug/libpthread.so.0
#1 0xb7eeecd0 in _L_mutex_lock_88 () from /usr/lib/debug/libpthread.so.0
/build/buildd/gdb-6.4.90.dfsg/gdb/dwarf2-frame.c:521: internal-error:
Unknown CFI encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
/build/buildd/gdb-6.4.90.dfsg/gdb/dwarf2-frame.c:521: internal-error:
Unknown CFI encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
(gdb) The program is running. Exit anyway? (y or n) y
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#414606: Stacktraces and deadlocked threads.,
which was filed against the libc6-dbg package.
It has been closed by Aurelien Jarno <aurelien@aurel32.net>.
Their explanation is attached below. If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact Aurelien Jarno <aurelien@aurel32.net> by replying
to this email.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Reply to: