X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sat, 29 May 2021 20:15:56 +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: <20210529172934.926A583B0DDA@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.21.2105292010460.2998@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>
 <alpine DOT DEB DOT 2 DOT 21 DOT 2105282107570 DOT 18480 AT nimbus> <alpine DOT DEB DOT 2 DOT 21 DOT 2105291653400 DOT 6833 AT nimbus> <20210529154754 DOT 6EE2283B0DDA AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 21 DOT 2105291905410 DOT 1084 AT nimbus> <20210529172934 DOT 926A583B0DDA AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
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
Precedence: bulk

On Sat, 29 May 2021, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> $ cat B42.sym
> v 20210407 2
> B 40000 40000 10000 10000 3 0 1 0 -1 -1 42 -1 -1 -1 -1 -1
> $ /usr/local/bin/gschem B42.sym
>
> (gschem:18810): libgedacairo-CRITICAL **: 19:24:50.981: file 
> edarenderer.c: line 585 (eda_renderer_draw_hatch): should not be reached
>
> (gschem:18810): libgedacairo-WARNING **: 19:24:50.982: 
> (edacairo.c:401):eda_cairo_stroke: code should not be reached

Exactly that should be fixed in current `master'.  I'm not sure if this 
was the cause for the problem you reported earlier, though, so it would be 
helpful if you could confirm that.

> so this "CRITICAL" error has probably been there a long time and might 
> not be that critical.

It is not.  The error simply means that there's an object with invalid 
data; it can safely be ignored.  Having a consistent object model was one 
of the main reasons that let me to creating libxornstorage, but ... oh 
well, I won't go into that.