X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 18 Jan 2017 11:57:06 +0100 (CET)
X-X-Sender:	igor2 AT igor2priv
To:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] [pcb] bugreport for 4.0.0
In-Reply-To:	<CAJXU7q9T2t3_7-QvXi65D1tveN-+qDc3Q1DioV4gamv9MHJ_kA@mail.gmail.com>
Message-ID:	<alpine.DEB.2.00.1701181152230.7286@igor2priv>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1701180741180 DOT 7286 AT igor2priv> <CAJXU7q9kVrXQhONbvxv+Frt=9hAqw8NyumT1tMtWV6wY-qywoQ AT mail DOT gmail DOT com> <CAJXU7q81VZuXHD+1XAkQscr5f+_npca521AMN4KphcwF0F_1mQ AT mail DOT gmail DOT com> <CAJXU7q9f-T5jy3mvGkLkwYO3HFTw4BfPVgaMxNYfMs53-cUqVg AT mail DOT gmail DOT com>
	<CAJXU7q_UZiZJh2DFQMoX7OMR=E8vLRc=3vARWsSR_hf2sPu1ag AT mail DOT gmail DOT com> <CAJXU7q9T2t3_7-QvXi65D1tveN-+qDc3Q1DioV4gamv9MHJ_kA AT mail DOT gmail DOT com>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
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

Hello Peter,

On Wed, 18 Jan 2017, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote:

>Hi Igor,
>Sorry for top posting (on my phone).

(no worries, I don't mind)

>The NoHoles (cached clipped polygon for rendering) could theoretically be
>null, with the valid flag set.
>
>"Clipped" could (should?) also be null, and if they are not NULL together,
>that probably suggests a bug in the no holes dicing routine, or (perhaps
>more likely) that the polygon data is invalid somehow.
>
>Null clipped polygons might occur if say, the polygon is small, and gets
>totally clipped away by other objects. Doesn't seem to apply in this case.
>
>I'm not sure from memory if we even call into the renderer if clipped ==
>NULL.
>
>I'll take a poke what happens on my experimental GL branches, as they don't
>use the NoHoles cache for rendering. Might give an extra data point.
>
>Will let you know if I find anything.
>

I also did some more code reading right after the previous mail a few 
hours ago and found that this might be the potential error:

clearPoly(), first if, returns 0 if on silk, but does not clear 
NoHolesValid (it does on the bottom, for a different case).

Caller is InitClip(), doesn't check the return value, so it doesn't clear 
NoHolesValid for that branch either.

So for the keep-silk-no-clearance case, I think we may need to change one 
of these. Didn't have the chance to try it yet.

Regards,

Igor2

- Raw text -