On Mon, Jan 02, 2006 at 12:00:03PM -0800, Daniel Burrows wrote:
> What does "info threads" show, and what do you get if you switch to
> each thread in turn (using "thread") and check the backtrace?
>
> Daniel
Unfortunately, "info threads" makes gdb exit (I don't know why), but here is
the captured "script" session. Also, I can reproduce this now just by
starting aptitude interactively and quitting immediately (start it,
press q, confirm quit with Enter).
I removed some of the control characters between starting aptitude and
the gdb interaction.
-Ivan
Script started on Tue Jan 3 00:09:29 2006
# gdb aptitude
GNU gdb 6.3.90_20051119-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/aptitude
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211798688 (LWP 5331)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
^[[?1049h^[[1;53r^[[m^[(B^[[4l^[[?7h^[[?1h^[=^[[39;49m^[[?1000h^[[?1h^[=[New
Thread -1211802704 (LWP 5334)]
^[[39;49m^[[m^[(B^[[H^[[2J[New Thread -1220191312 (LWP 5335)]
[New Thread -1228579920 (LWP 5336)]
Program received signal SIG32, Real-time event 32.
[Switching to Thread -1211802704 (LWP 5334)]
0xb7ea9421 in __read_nocancel () from /lib/tls/libpthread.so.0
(gdb) ^Gb^H ^H^Gcont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0xb7d99956 in __deregister_frame () from /lib/libgcc_s.so.1
(gdb) bt
#0 0xb7d99956 in __deregister_frame () from /lib/libgcc_s.so.1
#1 0xb7d6266a in dl_iterate_phdr () from /lib/tls/libc.so.6
#2 0xb7d9a646 in _Unwind_Find_FDE () from /lib/libgcc_s.so.1
#3 0xb7d97397 in _Unwind_DeleteException () from /lib/libgcc_s.so.1
#4 0xb7d98505 in _Unwind_Backtrace () from /lib/libgcc_s.so.1
#5 0xb7d9859a in _Unwind_ForcedUnwind () from /lib/libgcc_s.so.1
#6 0xb7eab002 in _Unwind_ForcedUnwind () from /lib/tls/libpthread.so.0
#7 0xb7ea8fc1 in __pthread_unwind () from /lib/tls/libpthread.so.0
#8 0xb7ea33e6 in sigcancel_handler () from /lib/tls/libpthread.so.0
#9 <signal handler called>
#10 0xb7ea9421 in __read_nocancel () from /lib/tls/libpthread.so.0
#11 0xb7ece983 in _nc_wgetch () from /lib/libncursesw.so.5
#12 0xb7ee21f3 in wget_wch () from /lib/libncursesw.so.5
#13 0xb7ecd745 in get_wch () from /lib/libncursesw.so.5
#14 0x081a869c in pkgSimulate::~pkgSimulate ()
#15 0x081a8780 in pkgSimulate::~pkgSimulate ()
#16 0xb7ea4cfd in start_thread () from /lib/tls/libpthread.so.0
#17 0xb7d2c19e in clone () from /lib/tls/libc.so.6
(gdb) info threads
5 Thread -1246118992 (LWP 5338) 0xb7ea6b91 in pthread_cond_wait@@GLIBC_2.3.2
() from /lib/tls/libpthread.so.0
4 Thread -1228579920 (LWP 5336) 0xb7ea6b91 in pthread_cond_wait@@GLIBC_2.3.2
() from /lib/tls/libpthread.so.0
3 Thread -1220191312 (LWP 5335) 0xb7eaa429 in do_sigwait ()
from /lib/tls/libpthread.so.0
1 Thread -1211798688 (LWP 5331) 0xb7ea5103 in pthread_join ()
from /lib/tls/libpthread.so.0
^[[?1000l^[[53;1H^[[?1049l^[[?1l^[>Ouch! Got SIGSEGV, dying..^M
Segmentation fault
^[]0;harpua^Gharpua:~# exit
Script done on Tue Jan 3 00:09:49 2006
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
