From: Tassilo Horn <tassilo@member.fsf.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Killing a frame sometimes kills emacs
Date: Thu, 01 Sep 2011 12:45:04 +0200 [thread overview]
Message-ID: <87sjog35jj.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m3mxeopn62.fsf@hase.home> (Andreas Schwab's message of "Thu, 01 Sep 2011 12:33:25 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Tassilo Horn <tassilo@member.fsf.org> 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?
As said in the reply to Eli, I don't have multiple displays. There's
only one X instance in which emacs runs with exactly one X11 frame.
Then I invoked "emacsclient -c" to get another X11 frame, and closing
that made emacs crash.
Bye,
Tassilo
next prev parent reply other threads:[~2011-09-01 10:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 20:16 Killing a frame sometimes kills emacs Tassilo Horn
2011-08-31 20:51 ` joakim
2011-08-31 23:06 ` chad
2011-09-01 2:53 ` Eli Zaretskii
2011-09-01 7:04 ` Tassilo Horn
2011-09-01 10:09 ` Tassilo Horn
2011-09-01 10:27 ` Eli Zaretskii
2011-09-01 10:42 ` Tassilo Horn
2011-09-01 10:56 ` Eli Zaretskii
2011-09-01 11:09 ` Tassilo Horn
2011-09-01 10:33 ` Andreas Schwab
2011-09-01 10:45 ` Tassilo Horn [this message]
2011-09-01 12:47 ` Jan D.
2011-09-01 13:05 ` Tassilo Horn
2011-09-01 15:29 ` Eli Zaretskii
2011-09-01 19:30 ` Ken Raeburn
2011-09-02 15:02 ` Andreas Schwab
2011-10-11 6:46 ` Tassilo Horn
2011-10-11 12:53 ` Stefan Monnier
2011-10-11 14:53 ` Tassilo Horn
2011-10-11 17:38 ` James Cloos
2011-10-11 19:17 ` Tassilo Horn
2011-10-11 19:49 ` Tassilo Horn
2011-10-12 2:04 ` Chong Yidong
2011-10-12 6:49 ` Tassilo Horn
2011-10-12 12:57 ` Stefan Monnier
2011-11-17 10:10 ` Tassilo Horn
2011-11-17 11:18 ` Chong Yidong
2011-11-17 13:45 ` Tassilo Horn
2011-11-17 16:34 ` Paul Eggert
2011-11-17 16:58 ` Tassilo Horn
2011-11-18 2:41 ` Chong Yidong
2011-11-18 2:05 ` Stefan Monnier
2011-11-18 9:38 ` Tassilo Horn
2012-01-20 23:29 ` andres.ramirez
2012-01-21 0:34 ` Glenn Morris
2012-01-21 8:02 ` andres.ramirez
2012-01-20 23:29 ` andres.ramirez
2011-10-11 17:56 ` Jan Djärv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjog35jj.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).