From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: emacs --daemon and GDK default display
Date: Mon, 23 Mar 2009 18:09:36 +0100 [thread overview]
Message-ID: <49C7C250.9030505@swipnet.se> (raw)
In-Reply-To: <18887.22064.669003.766051@a1i15.kph.uni-mainz.de>
Ulrich Mueller skrev:
>>>>>> On Tue, 17 Mar 2009, Jason Rumney wrote:
>>> While I think that the blame is with libcanberra, I'm confused
>>> about the fact that the segfault only happens during the second
>>> request from a client. Does it mean that there is a GDK default
>>> display at the time of the first request, but not for the second
>>> one? Why?
>
>> Just a guess without looking at libcanberra, but could the bug be
>> that libcanberra remembers the default display created during the
>> first request and tries to reuse it after it is closed?
>
> It doesn't remember it. libcanberra just calls a GTK function, which
> in turn asks the GDK display manager for the default display. And that
> returns a valid display for the first request, but a null pointer for
> the second one.
>
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. Note that closing displays under Gtk+ is generally buggy in
itself. If you can capture a stack trace in the debugger we should be able to
tell if it is Gtk+ or Emacs that is doing the wrong thing.
Jan D.
next prev parent reply other threads:[~2009-03-23 17:09 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 [this message]
2009-03-23 21:33 ` Ulrich Mueller
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=49C7C250.9030505@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=ulm@gentoo.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.