Your message dated Sun, 23 Jul 2006 23:20:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#276596: ptrace / thread_db_get_info errors when debugging
ryhtmbox
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gdb
Version: 6.1-3
Severity: normal
Hi,
It's quite difficult to debug the crasing of rhythmbox when it exits
because gdb has huge problems following the threads created by
rhythmbox. Typically, when rhythmox exits, I get things like:
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...[New Thread 1133976496 (LWP 24679)]
[Thread 1133976496 (LWP 24679) exited]
[Thread 1116904368 (zombie) exited]
[Thread 1108515760 (LWP 24674) exited]
[Thread 1125292976 (zombie) exited]
ptrace: No such process.
thread_db_get_info: cannot get thread info: generic error
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
thread_db_get_info: cannot get thread info: generic error
(gdb) The program is running. Exit anyway? (y or n) y
Quitting: thread_db_get_info: cannot get thread info: generic error
bee%
Today, for the first time, I could run rhythmbox TWICE from within gdb
without gdb deciding it was enough! Usually, 99% of the time, gdb
can't handle the death if rhythmbox.
Should I attach a gdb to gdb? What should I look for? (I'm scared.)
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
Versions of packages gdb depends on:
ii libc6 2.3.2.ds1-17 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libreadline4 4.3-13 GNU readline and history libraries
-- no debconf information
Regards,
--
Loïc Minier <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---
On Fri, Oct 15, 2004 at 04:27:53PM +0200, Loïc Minier wrote:
> I've looked in upstream BTS, and found a close related bug, but
> couldn't reproduce it, so I indicated that in a new bug report. I did
> not get a bugid though, I presume because there's some form of
> moderation. I'll keep you informed.
I am fairly sure this is fixed in the GDB in unstable now. I can't
reproduce it, anyway.
--
Daniel Jacobowitz
CodeSourcery
--- End Message ---
