[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: crash: x_error_quitter
From: |
Richard Stallman |
Subject: |
Re: crash: x_error_quitter |
Date: |
Wed, 16 May 2007 10:32:50 -0400 |
The stack frames will usually not get affected. But the return
address might be completely wrong, and that will affect gdb's idea of
what function the stack frame belongs to, and what variables are
stored in what registers at that point of time.
It probably won't matter, because we aren't going to try to debug the
Xlib functions themselves. We want to know which Xlib function Emacs
called, and how.
However, we should turn off the NO_RETURN for this.
(It seems to be on x_connection_closed.)
I think that if we are compiling with -g, we should also enable the
-fno-crossjumping option.
I always use -O0 -fnoinline, for maximum debuggability.
But that shouldn't matter for this bug. The backtrace
should give the info we need, presuming (x-synchronize t)
was done.
- Re: crash: x_error_quitter, (continued)
- Re: crash: x_error_quitter, Chong Yidong, 2007/05/13
- Re: crash: x_error_quitter, Jan Djärv, 2007/05/13
- Re: crash: x_error_quitter, Chong Yidong, 2007/05/13
- Re: crash: x_error_quitter, Jan Djärv, 2007/05/13
- Re: crash: x_error_quitter, Richard Stallman, 2007/05/14
- Re: crash: x_error_quitter, David Kastrup, 2007/05/14
- Re: crash: x_error_quitter, Richard Stallman, 2007/05/15
- Re: crash: x_error_quitter, David Kastrup, 2007/05/15
- Re: crash: x_error_quitter, Richard Stallman, 2007/05/15
- Re: crash: x_error_quitter, David Kastrup, 2007/05/16
- Re: crash: x_error_quitter,
Richard Stallman <=
- Re: crash: x_error_quitter, Eli Zaretskii, 2007/05/16
- Re: crash: x_error_quitter, David Kastrup, 2007/05/16