The problem is only reproducible after e.g. installing a package; just 
starting aptitude and quitting straight away does not reproduce it.

A backtrace for this issue looks as follows:

(gdb)
#0  0xf760fa60 in ?? () from /lib/libgcc_s.so.1
#1  0xf7610278 in ?? () from /lib/libgcc_s.so.1
#2  0xf7610304 in _Unwind_ForcedUnwind () from /lib/libgcc_s.so.1
#3  0xf783d814 in _Unwind_ForcedUnwind () from /lib/libpthread.so.0
#4  0xf783adfc in __pthread_unwind () from /lib/libpthread.so.0
#5  0xf7830eec in sigcancel_handler () from /lib/libpthread.so.0
#6  <signal handler called>
#7  0xf783c908 in do_sigwait () from /lib/libpthread.so.0
#8  0xf783c9b4 in sigwait () from /lib/libpthread.so.0
#9  0xf7bcaa44 in cwidget::toplevel::signal_thread::operator()() const ()
   from /usr/lib/libcwidget.so.3
#10 0xf7bcaa98 in void* 
cwidget::threads::thread::bootstrap<cwidget::toplevel::signal_thread>(void*) 
() from /usr/lib/libcwidget.so.3
#11 0xf7832358 in start_thread () from /lib/libpthread.so.0
#12 0xf7571f1c in ?? () from /lib/libc.so.6
#13 0xf7571f1c in ?? () from /lib/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

This was without debugging symbols installed. If you'd like a backtrace 
with -dbg packages installed or additional info, please let me know.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to