Re: gdk_display_close problems ...

[Philipp Lohmann - Sun Germany - ham02 - Hamburg <Philipp Lohmann Sun COM>]

Hi,

then the immediate workaround will be to not close the display. Not 
nice, but should work ?

Regards, pl

Matthias Clasen wrote:
> > Hi there,
> >
> > 	So - I've been debugging an embarassing set of problems with
> > gdk_display_close. I'm assuming that in gtk+ for some reason we let a
> > number of GdkDisplay refs float around the place so that the display is
> > never finalized, and we only dispose it once (with the 'closed' guard).
> >
> > 	However - quite a simple program will provoke a SEGV eg.
> >
> > #include <gtk/gtk.h>
> >
> > int
> > main (int argc, char **argv)
> > {
> > 	GdkDisplay *display;
> > 	gtk_init (&argc, &argv);
> > 	display = gdk_display_open (":0.0");
> > 	gdk_display_close (display);
> > 	return 0;	
> > } 
>
>
> Closing displays doesn't work. Nobody got around to fixing it yet. 
> See http://bugzilla.gnome.org/show_bug.cgi?id=85715

--
The major difference between a thing that might go wrong and a thing
that cannot possibly go wrong is that when a thing that cannot possibly
go wrong goes wrong, it usually turns out to be impossible to get at
or repair.   -- Douglas Adams