On Fri, Mar 12, 2010 at 10:40:40PM +0100, Frans Pop elen...@planet.nl was
heard to say:
On Friday 12 March 2010, Daniel Burrows wrote:
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
On Monday 15 March 2010, Daniel Burrows wrote:
Hm, the threadall backtraces look identical. Is there another page?
Ugh, must have made a mistake. Will get a new trace.
BTW, if you're talking about the mouse having problems because of the
terminal state: usually holding down Shift
On Monday 15 March 2010, Daniel Burrows wrote:
Hm, the threadall backtraces look identical. Is there another page?
Shift did work...
I've cleaned out the remnants of the frontend.
Thread 12 (Thread 0xf3dddb70 (LWP 1516)):
#0 0xf7837acc in pthread_cond_wait@@GLIBC_2.3.2 () from
On Sun, Feb 28, 2010 at 02:09:09PM +0100, Frans Pop elen...@planet.nl 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
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
5 matches
Mail list logo
