Re: [gtk-list] Re: Window close signal

["Francois JEANMOUGIN" <pingouin crystal u-strasbg fr>]

On Jan 19,  9:25am, Owen Taylor wrote:
[...]
> With (from killing a GTK application)
>
> ** ERROR **: sigpipe caught
>
> The same thing is happening. And it is being caught the same way.
> The error message is just a bit different.

	Hem, perhaps I have to update my Gtk or is it an Afterstep bug :

** ERROR **: an x io error occurred
IOT trap/Abort (core dumped)

	But it is different if I display it on my SGI (the app run on a Linux
box, so, only the wm is different). In this case, the wm never make such kill
event, all the ways are clean. So I will discuss with Guylhem where could it
come from, but this seems to be wm dependant.

	Could you please send me what X events you are waiting for and which
one is "bad", i.e. what could be different? I would then be able to discuss
with the Afterstep guys (or you want to contact them directly?).

[...]
> Any end-user probably should have ulimit -c 0

	Yep, it's a solution ;-).

> We can probably make the exit a bit smoother though. We can
> set a "connection_exists" variable and not do X cleanup if
> it the connection has been lost.

	But we first have to be sure that the event is not due to something
else than Gtk...

							Sorry,
								Francois.

-- 
Francois Jeanmougin     | groupe de bioinformatique / bioinformatics groupe
tel:(+33) 3 88 65 32 71 | IGBMC BP 163 67404 Illkirch France
e-mail: jeanmougin@igbmc.u-strasbg.fr
"Ce sont des desespoirs d'intellectuels ennuyes, ou des ennuis 
d'intellectuels desesperes, comme vous voulez, comme vous voulez" M. Benin