[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crashes of GNU Emacs 23
From: |
Jan D. |
Subject: |
Re: Crashes of GNU Emacs 23 |
Date: |
Thu, 7 Jul 2005 11:41:56 +0200 |
What you need to do is start emacs under gdb in the Emacs source
directory.
Doesn't work so fine ...
From within stable GNU Emacs 22.0.50 I get in the *gud-emacs* buffer:
I don't think Jan is saying start gdb "in Emacs".
No, sorry if I was unclear. From what I see the gdb session is not
started in the Emacs src directory. Do something like this:
% cd emacs/src
% gdb emacs
...
Breakpoint 1 at 0x814814c: file emacs.c, line 461.
Breakpoint 2 at 0x811bf10: file xterm.c, line 7795.
(gdb)
The last two lines indicate that the breakpoints in .gdbinit has been
set correctly. Then just run emacs:
(gdb) r
and call (x-synchronize t) in Emacs (it will make Emacs much slower).
When the breakpoint in x_error_quitter is hit, then do a stack trace.
You can also step a couple of times in x_error_quitter (n command in
gdb) until you come to this line:
x_connection_closed (display, buf1);
There you just
(gdb) p buf1
so we can see that it is the same error.
Jan D.
- Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/06
- Re: Crashes of GNU Emacs 23, Nick Roberts, 2005/07/07
- Re: Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/07
- Re: Crashes of GNU Emacs 23,
Jan D. <=
- Re: Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/07
- Re: Crashes of GNU Emacs 23, Jan D., 2005/07/07
- Re: Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/07
- Re: Crashes of GNU Emacs 23, Jan D., 2005/07/07
- Re: Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/07
- Re: Crashes of GNU Emacs 23, Jan D., 2005/07/08
- Re: Crashes of GNU Emacs 23, Peter Dyballa, 2005/07/08
- Re: Crashes of GNU Emacs 23, Jan D., 2005/07/13