[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs --daemon and GDK default display
From: |
Ulrich Mueller |
Subject: |
Re: emacs --daemon and GDK default display |
Date: |
Mon, 23 Mar 2009 10:28:16 +0100 |
>>>>> 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.
Ulrich
- emacs --daemon and GDK default display, Ulrich Mueller, 2009/03/17
- Re: emacs --daemon and GDK default display, Jason Rumney, 2009/03/17
- Re: emacs --daemon and GDK default display,
Ulrich Mueller <=
- Re: emacs --daemon and GDK default display, Jan Djärv, 2009/03/23
- Re: emacs --daemon and GDK default display, Ulrich Mueller, 2009/03/23
- Re: emacs --daemon and GDK default display, Jan Djärv, 2009/03/25
- Re: emacs --daemon and GDK default display, Jan Djärv, 2009/03/28
- Re: emacs --daemon and GDK default display, Ulrich Mueller, 2009/03/28
- Re: emacs --daemon and GDK default display, Austin, 2009/03/23