Delivered-To: garrigue at math.nagoya-u.ac.jp Authentication-Results: mailhost.math.nagoya-u.ac.jp sender=lablgtk-bounces at yquem.inria.fr; domainkey=neutral (no query protocol specified; no policy for yquem.inria.fr) Delivered-To: Lablgtk at yquem.inria.fr DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=AwtLY6hT+Xs6DVjwLG8x9dFUp46JVwz7h7GfSfmgt8c=; b=FU0ALXkFYfYflRfgTkSVWuIeN0W8ZuRME8y9GS0gCvmEVrP6OoWOQDzNzNOFDhBtZg McVt2WpSmFRvOPGiguZ2BOS3IMpY4WzITlb8hVh85ZwiBWEpreFMOHR+HoxcfVFbpZQZ 2xdxhhY7RjgpzLafqLpWaj8xJmrOvGU11zK3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=re+ANfJBlVaskiVJlzwxk//63WQ//k/ljJWfbK53Loc34jmLnFiv3mx5FhfJZHXCup 39hu3LnbPnO75lEZDZL/WkmDgVoJr+LYGJ5TCAvhFhQm98/HRYiBwkZpzkSb0SGC1QfV Gsikhp6SW8wHz8ctaAAayUYJue+U+jLD/zThU= MIME-Version: 1.0 In-Reply-To: References: <20100913205658.026ac951.pdgroves at gmail.com> <20100914154914.9a890dc1.pdgroves@gmail.com> <20100914185304.67bedad5.pdgroves@gmail.com> Date: Wed, 15 Sep 2010 18:53:35 +0900 Message-ID: Subject: Re: [Lablgtk] segfault when reattaching a tree model to a tree view From: Jacques Garrigue To: Peter Groves Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Lablgtk at yquem.inria.fr Status: U On Wed, Sep 15, 2010 at 5:02 PM, Peter Groves wrote: > Jacques, > > You're example ran fine (once i ran it properly :). I noticed (through > brute force guess and check) that in my code I was able to work around > the bug by changing the vpolicy on the scroll bar to `ALWAYS instead > of `AUTOMATIC. > > After much trial and error to bring your example in line with my code, > I have been able to reproduce the bug with as few changes as possible > to your example. The code is attached. The program should crash when > you click the 'dump' button. In the current form, you can make the bug > =A0go away by either > 1) changing the vpolicy of the scroll_window to 'ALWAYS on line 142, > OR > 2) you can remove the call to scrollContainer#set_resize_mode > `IMMEDIATE; on line 140. Removing this spurious scrollContainer seems to do the trick too. More curiously, actually I don't get a segmentation fault, but the complete window disappears and is restarted immediately. This is maybe the way it is handled under windows (I happen to be testing under windows because I was building the windows package of lablgtk2...) > For me, the workaround of setting the vpolicy to `ALWAYS is > acceptable. Sadly, this whole exercise has not led to a speed increase > in the slowness I was originally trying to solve, but hopefully the > bug report does some good. SInce this seems to be a bug in gtk, I'm afraid I can do little about that. With a C translation of this code, maybe I can file a bug report, but honestly who wants to translate this kind of code to C... For the performance, this is too bad. If the problem is specific to lablgtk= , we can try to do something, but I'm afraid this is just the utter inneficie= ncy of the gtk's stores. Jacques _______________________________________________ Lablgtk mailing list Lablgtk@yquem.inria.fr http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk