X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Fri, 28 May 2021 21:19:12 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] errors in git gschem
In-Reply-To:	<20210528184745.C32D183B0DDA@turkos.aspodata.se>
Message-ID:	<alpine.DEB.2.21.2105282107570.18480@nimbus>
References:	<20210527152030 DOT 03D81832CA7E AT turkos DOT aspodata DOT se> <20210528121930 DOT 617BC83B0DDA AT turkos DOT aspodata DOT se> <20210528160449 DOT 9E70083B0DDA AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 21 DOT 2105281922160 DOT 14690 AT nimbus> <20210528184745 DOT C32D183B0DDA AT turkos DOT aspodata DOT se>
User-Agent:	Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 28 May 2021, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> git pull and the seg fault is gone, nice!

Thank you for verifying!

> (gschem:28242): libgedacairo-CRITICAL **: 20:12:29.140: file 
> edarenderer.c: line 678 (eda_renderer_draw_pin): should not be reached
> [...]

Ok, so the problem with invalid OBJECT structs being rendered still 
persists.

> Now, theese sets of messages comes as a group when e.g. moving the
> mouse pointer from outside to the inside of the gschem window and
> reverse, but not if I first click in e.g. the message window.
>
> Ditto, switching virtual displays, virtual terminal, and when
> clicking inside various parts of gschem like alternativly
> clicking in docks and main (canvas) window.

This looks like the messages appear whenever the page is rendered, which 
would indicate that the invalid objects are part of the page (as opposed 
to some invalid intermediate state while loading/closing the page).

Hmm.  I'll have to look into this tomorrow.

> Ok, new log with current gschem at:
> http://aspodata.se/tmp/valgrind_memcheck_gschem_3_log

Ah, thanks.  The fmin issue is still there, which makes sense since you 
probably hadn't applied my second patch yet, but more importantly, the 
segfault-related issues are gone.

- Raw text -