Bug 468266

--- Additional comment from lpoetter on 2008-10-23 15:45:38 EDT ---

Indeed, "info threads" works after installing those debug symbols for glibc,

Segfaults and borkage isn't fixed though. I tried to track down bug 467651 a bit. No luck, gdb fails right-aways when opreport segfaults. A debugger that crashes when the debugged program crashes is pretty pointless, isn't it?

49 [lennart@lambda] ~$ gdb --args opreport -l /home/lennart/projects/pulseaudio/src/.libs/lt-pulseaudio 
GNU gdb Fedora (6.8-24.fc10)
Copyright (C) 2008 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 "i386-redhat-linux-gnu"...
(gdb) r
Starting program: /usr/bin/opreport -l /home/lennart/projects/pulseaudio/src/.libs/lt-pulseaudio
warning: [vdso] (tgid:30206 range:0x110000-0x111000) could not be found.
warning: [vdso] (tgid:32384 range:0x110000-0x111000) could not be found.
warning: [vdso] (tgid:32553 range:0x110000-0x111000) could not be found.
warning: [vdso] (tgid:5805 range:0x110000-0x111000) could not be found.
CPU: Core Solo / Duo, speed 1000 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Unhalted clock cycles) with a unit mask of 0x00 (Unhalted core cycles) count 100000
../../gdb/buildsym.c:1281: internal-error: buildsym_init: Assertion `! pending_addrmap' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

../../gdb/buildsym.c:1281: internal-error: buildsym_init: Assertion `! pending_addrmap' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted
50 [lennart@lambda] ~$