Re: Reproducible gtk crash

[Simon Josefsson]

Miles Bader <address@hidden> writes:

> It might be quicker to just recompile xterm.o without optimization (I
> usually just remove the file, run make again to see what compiler
> command line it uses, then execute that command manually without the
> -O option and finally run make to re-link).

I'll do a clean rebuild with CFLAGS=-g and see if it still breaks.

Btw, sometimes it crashes gdb as well:

[Thread debugging using libthread_db enabled]
[New Thread 1083202432 (LWP 441)]
[New Thread 1112292272 (LWP 480)]
[New Thread 1112820656 (LWP 481)]
[New Thread 1113156528 (LWP 482)]
/nevyn/local/gdb/gdb-6.1/gdb/lin-lwp.c:1503: internal-error: lin_lwp_wait: 
Assertion `iterate_over_lwps (running_callback, NULL)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

/nevyn/local/gdb/gdb-6.1/gdb/lin-lwp.c:1503: internal-error: lin_lwp_wait: 
Assertion `iterate_over_lwps (running_callback, NULL)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
(gdb) bt
Cannot fetch general-purpose registers for thread 1083202432: generic error
(gdb) q
The program is running.  Exit anyway? (y or n) y
Quitting: thread_db_get_info: cannot get thread info: generic error