Delivered-To: lablgtk at yquem.inria.fr
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: =?iso-8859-1?Q?RE=A0=3A_=5BLablgtk=5D_Segfault_when_removing_or_setting_a?=
	=?iso-8859-1?Q?n_invalid_GTree=2Eiter?=
Date: Sun, 3 Aug 2008 20:56:35 +0200
Message-ID: <5EFD4D7AC6265F4D9D3A849CEA9219190141A9 at LAXA.intra.cea.fr>
Thread-Topic: [Lablgtk] Segfault when removing or setting an invalid GTree.iter
Thread-Index: Acj1e9SLcVkzirwfQHaeACLns037fwAHX0jL
References: <b6a766a0808030815i21b95c38x29c22e9d03681a5a at mail.gmail.com>
From: "MONATE Benjamin 205998" <Benjamin.MONATE at cea.fr>
To: "Guillaume Brunerie" <guillaume.brunerie at gmail.com>,
        <lablgtk@yquem.inria.fr>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Length: 620

Hi Guillaume,

You program is breaking Gtk invariants hence the "Gtk-CRITICAL" message: =
GTree.iter cannot be used if Gtk has decided they are invalid.
Gtk is by defaul a little sloppy about ctitical errors. It just displays =
the messsages and goes on even if an internal later segfault may occur.
If you want your program to stop you may add to the start of bug.ml:
Glib.Message.set_always_fatal [ `CRITICAL; `ERROR; `FLAG_FATAL; =
`FLAG_RECURSION];;


Benjamin Monate

_______________________________________________
Lablgtk mailing list
Lablgtk@yquem.inria.fr
http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk