X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=J9NTF3O8ZMuq/5MZv3SQdytEqfTsdRAA84QsFRK909U=;
	b=iWWvXF/c38f6JzBpo45CCmXAFS0J3GuT/GJ2lnk/0tMB/30y0neuykhXkTV5nOjEMD
	C5Rxx+Ov9EVAPGdRsiAJCg53VmS2jEnI1PvW/wu2B6fEQFcELImSVy8YQ3ze3kqsyjtI
	CXaOiLPOk1C8nkbIXcgYq4wGml/iSulCSD+grjFj7og7e+zI5fTR1IBsSDc0C0G9aLVq
	jXwEbjNJ89oxjvTr4VtmL9n6QApJDx1yAZ7iOjrybJaStIHDtkjlsTPBQ3v3b1o0pND8
	xnAH1K2PiOlLf083uZ10Y8dEL5wTGcsSp2iNFR/vdvYyVE44QMTrWyOwkEeT677nMKGy
	oMqg==
MIME-Version:	1.0
X-Received:	by 10.180.72.242 with SMTP id g18mr1370012wiv.7.1387438180915;
	Wed, 18 Dec 2013 23:29:40 -0800 (PST)
In-Reply-To:	<201312190608.rBJ68W4d021122@envy.delorie.com>
References:	<CALT8Ef5XtuaPY4QjAw=658ZaL_sV38CbX0aqgosRvOVdG5BmKA AT mail DOT gmail DOT com>
	<201312190608 DOT rBJ68W4d021122 AT envy DOT delorie DOT com>
Date:	Thu, 19 Dec 2013 12:59:40 +0530
Message-ID:	<CALT8Ef7vad7zZZ+W1DaH=L5Qjo=xRbqL5=fy1==V19T8iR-+xQ@mail.gmail.com>
Subject:	Re: [geda-help] PCB segfault on opening specific PCBs
From:	Shashank Chintalagiri <shashank DOT chintalagiri AT gmail DOT com>
To:	geda-help AT delorie DOT com
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--f46d043c0816ebe35604edde1f82
Content-Type: text/plain; charset=ISO-8859-1

I was able to workaround the problem for the moment by nuking everything
contained in NetList()(). I could not find a corresponding bug report on
launchpad, though at the moment I'm somewhat uncertain about the actual
cause / source of the problem. The following facts contradict the
explanation you suggest :

* PCB was working fine until some moment in time.
* PCB saved, exited, gsch2pcb run which generated (in my case)
x-smu.pcb.bak8
* New x-smu.pcb fails to open. However, x-smu.pcb.bak8 _also_ fails to
open, suggesting the problem precedes gsch2pcb
* On removing NetList()(...), x-smu.pcb opens fine.
* Load Netlist from file doesn't cause a crash.
* Saving the file now, exiting, and reopening the file does not cause a
crash. This implies that the new netlist that gnetlist made isn't
inherently bad.

I'm therefore hesitant to claim that the fault lies in CreateNewNet() and
the names coming from the schematic. If I had to guess I would say it was
pcb that for some reason saved a corrupted version of the file the first
time around.

I can provide the corresponding pcb files to you off-list if you like. I've
kept copies of the ones that cause a crash atleast.

Thanks
Shashank


On Thu, Dec 19, 2013 at 11:38 AM, DJ Delorie <dj AT delorie DOT com> wrote:

>
> Looks like CreateNewNet() has a hardcoded limit of 63 characters for
> net names, but doesn't check the length coming from the schematic.
> Did you add or rename a net using a long name?  Or are you using
> heirarchy?
>
> (and yes, please add a bug report to launchpad if there isn't one already)
>



-- 

Chintalagiri Shashank
Indian Institute of Technology, Kanpur

http://blog.chintal.in

--f46d043c0816ebe35604edde1f82
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>I was ab=
le to workaround the problem for the moment by nuking everything contained =
in NetList()(). I could not find a corresponding bug report on launchpad, t=
hough at the moment I&#39;m somewhat uncertain about the actual cause / sou=
rce of the problem. The following facts contradict the explanation you sugg=
est :<br>
<br></div>* PCB was working fine until some moment in time.<br></div>* PCB =
saved, exited, gsch2pcb run which generated (in my case) x-smu.pcb.bak8<br>=
</div>* New x-smu.pcb fails to open. However, x-smu.pcb.bak8 _also_ fails t=
o open, suggesting the problem precedes gsch2pcb<br>
</div>* On removing NetList()(...), x-smu.pcb opens fine.<br></div>* Load N=
etlist from file doesn&#39;t cause a crash.<br></div>* Saving the file now,=
 exiting, and reopening the file does not cause a crash. This implies that =
the new netlist that gnetlist made isn&#39;t inherently bad.<br>
<br></div>I&#39;m therefore hesitant to claim that the fault lies in Create=
NewNet() and the names coming from the schematic. If I had to guess I would=
 say it was pcb that for some reason saved a corrupted version of the file =
the first time around.<br>
<br></div>I can provide the corresponding pcb files to you off-list if you =
like. I&#39;ve kept copies of the ones that cause a crash atleast.<br><br><=
/div>Thanks<br></div>Shashank<br></div><div class=3D"gmail_extra"><br><br>
<div class=3D"gmail_quote">On Thu, Dec 19, 2013 at 11:38 AM, DJ Delorie <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:dj AT delorie DOT com" target=3D"_blank">dj AT d=
elorie.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Looks like CreateNewNet() has a hardcoded limit of 63 characters for<br>
net names, but doesn&#39;t check the length coming from the schematic.<br>
Did you add or rename a net using a long name? =A0Or are you using<br>
heirarchy?<br>
<br>
(and yes, please add a bug report to launchpad if there isn&#39;t one alrea=
dy)<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><br>Chintalagiri Shasha=
nk<br>Indian Institute of Technology, Kanpur<br><br><a href=3D"http://blog.=
chintal.in" target=3D"_blank">http://blog.chintal.in</a><br><br>
</div>

--f46d043c0816ebe35604edde1f82--

- Raw text -