From: Ulrich Mueller <ulm@gentoo.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: emacs --daemon and GDK default display
Date: Mon, 23 Mar 2009 22:33:38 +0100 [thread overview]
Message-ID: <18888.50.303190.358177@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <49C7C250.9030505@swipnet.se>
>>>>> On Mon, 23 Mar 2009, Jan Djärv wrote:
> If I remember correctly, the display manager does not set a new
> default display when the old is closed. There is some code for that
> case i gtkutil.c.
> But there was a bug in it. I don't know if that fixes anything, but
> please try again.
This wouldn't help, since the segmentation fault already happens in
gdk_display_open, so it doesn't reach the code affected by your
change of today.
> Note that closing displays under Gtk+ is generally buggy in itself.
> If you can capture a stack trace in the debugger
A GDB backtrace is attached to our downstream bug at
<http://bugs.gentoo.org/attachment.cgi?id=185188>. Unfortunately,
without symbols in Emacs. ;-) But I think that there's enough
information to see what is going on.
> we should be able to tell if it is Gtk+ or Emacs that is doing the
> wrong thing.
There's definitely a problem in libcanberra which fails to check for a
null pointer (already reported to its upstream).
The question is if Emacs could do anything to work around the problem?
I suppose you can't set a default display before calling
gdk_display_open?
Ulrich
next prev parent reply other threads:[~2009-03-23 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 11:14 emacs --daemon and GDK default display Ulrich Mueller
2009-03-17 11:47 ` Jason Rumney
2009-03-23 9:28 ` Ulrich Mueller
2009-03-23 17:09 ` Jan Djärv
2009-03-23 21:33 ` Ulrich Mueller [this message]
2009-03-25 19:21 ` Jan Djärv
2009-03-28 15:49 ` Jan Djärv
2009-03-28 18:09 ` Ulrich Mueller
2009-03-24 1:11 ` Austin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18888.50.303190.358177@a1ihome1.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=jasonr@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.