[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Killing a frame sometimes kills emacs
From: |
Andreas Schwab |
Subject: |
Re: Killing a frame sometimes kills emacs |
Date: |
Thu, 01 Sep 2011 12:33:25 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) |
Tassilo Horn <address@hidden> writes:
> It turned out to be a crash, not something calling Fkill_emacs. Here's
> the backtrace:
>
> Breakpoint 1 at 0x4f23dd: file emacs.c, line 1985.
> Starting program: /usr/bin/emacs-24
> [Thread debugging using libthread_db enabled]
> [New Thread 0x7fffe6e80700 (LWP 31725)]
> [New Thread 0x7fffe667f700 (LWP 31726)]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff4dd1ecc in XFreeColormap () from /usr/lib64/libX11.so.6
> #0 0x00007ffff4dd1ecc in XFreeColormap () from /usr/lib64/libX11.so.6
> No symbol table info available.
> #1 0x00007ffff759c93a in ?? () from /usr/lib64/libgdk-3.so.0
Isn't that the known gtk bug with multiple displays?
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- Re: Killing a frame sometimes kills emacs, Tassilo Horn, 2011/09/01
- Re: Killing a frame sometimes kills emacs,
Andreas Schwab <=
- Re: Killing a frame sometimes kills emacs, Tassilo Horn, 2011/09/01
- Re: Killing a frame sometimes kills emacs, Jan D., 2011/09/01
- Re: Killing a frame sometimes kills emacs, Tassilo Horn, 2011/09/01
- Re: Killing a frame sometimes kills emacs, Eli Zaretskii, 2011/09/01
- Re: Killing a frame sometimes kills emacs, Ken Raeburn, 2011/09/01
- Re: Killing a frame sometimes kills emacs, Andreas Schwab, 2011/09/02