On Sun, Feb 28, 2010 at 02:09:09PM +0100, Frans Pop <[email protected]> was
heard to say:
> 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:
Just from looking at the backtrace, it looks like the
cwidget signal-processing thread is being canceled when you quit, but
crashing in the process. But the thread should be stopped cleanly
before the program quits. Unless, maybe, the program is crashing for
some other reason (e.g., due to an uncaught exception or another
signal).
> This was without debugging symbols installed. If you'd like a backtrace
> with -dbg packages installed or additional info, please let me know.
I think a backtrace with -dbg packages would be useful. So would
a backtrace of all threads ("thread apply all backtrace"); I'd like
to see what the main thread is up to.
Daniel
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
