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=ftbNCEZ9CfxwOJfiZfxwk5B/vw+pRw61zAbemI+d0PM=; b=jewoIPIMBdb/2XHWDoOovdYl88s2gJ9/pc/XJcVxIiKI0Unw6tbl3cG9KKfLWwMdJa rRvqe18+rc5BLumDfSo0F5UbNyzCEqu54vVd8yU4PMIG0kTjOlC5aG6FMhjAAf+2t2I5 6ypUbNK52yQfKT0YGPju/oPRK2GkzvSBY23gN5clcfh7R+dKHz26p9fXhBswz1M38h4V gZTXCcErHwNh1VRj0KRur+xU7WaFHDFLk35ISUlGEWYBx9WZY+Rmo0mTT/wkOohbQj69 MeL23x9coiyQpc9o+sjXcb/2SY/jHRea/wJMWbYKjEuZkHaFgeTFcnqMuaPt+/jQ4V9Q eG3w== MIME-Version: 1.0 In-Reply-To: <4F6B1276.80507@laserlinc.com> References: <4F6B1276 DOT 80507 AT laserlinc DOT com> Date: Thu, 22 Mar 2012 13:10:02 +0000 Message-ID: Subject: Re: [geda-help] Segfault in gnetlist From: Thomas Oldbury To: geda-help AT delorie DOT com Content-Type: multipart/alternative; boundary=20cf30334f8f37b5b304bbd4a0b3 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 Precedence: bulk --20cf30334f8f37b5b304bbd4a0b3 Content-Type: text/plain; charset=ISO-8859-1 Hi Joshua, thanks for the reply I eventually traced it down to a component with a stray new line in the value property. I fixed this and it now works fine. Thanks for your help On 22 March 2012 11:52, Joshua Lansford wrote: > Hi Tom, > Was looking though the list and saw your request and it doesn't look like > you have a response. > I haven't taken a detailed look at your schematic, but I have found that > gnetlist will segfault whenever there is an empty property in the schematic > or one of the symbols. It made me panic the first time I hit it. Now > fixing the problem is routine. This grep command like this should find it, > and then you can remove it with vim or another text editor. > grep -n =\\s*$ *.sch > ~Joshua > > > On 03/16/2012 08:54 PM, Thomas Oldbury wrote: > >> Trying to load a schematic into xgsch2pcb results in a blank PCB file. >> >> Traced it down to a segfault here: >> >> $ gnetlist -q -g gsch2pcb -o FreeBox.new.pcb -m gnet-gsch2pcb-tmp.scm >> power_main.sch >> Segmentation fault >> >> I can delete a small section of my schematic and it goes away (generally >> around the lower optocoupler area); however, if I replace it and delete >> another section around the same area, it also goes away! Also, it seems >> (although it may just be me) that deleting parts individually doesn't >> work... you have to delete all at once?! This has made trying to find an >> individually faulty part hard, so I think it's probably some combination of >> factors that I'm unlucky enough to trip over. >> >> I have attached my schematic in case it helps, it uses a few custom >> symbols but the bug should still show up. >> >> Is there a way for me to track down what part is causing the problem... >> never had this before with gEDA. >> >> Thanks, >> Tom >> > --20cf30334f8f37b5b304bbd4a0b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Joshua, thanks for the reply

I eventually traced it down to a com= ponent with a stray new line in the value property. I fixed this and it now= works fine.

Thanks for your help

On 22 March 2012 11:52, Joshua Lansford <Joshua DOT Lansford AT laserlinc DOT com> wrote:
Hi Tom,
=A0Was looking though the list and saw your request and it doesn't loo= k like you have a response.
I haven't taken a detailed look at your schematic, but I have found tha= t gnetlist will segfault whenever there is an empty property in the schemat= ic or one of the symbols. =A0It made me panic the first time I hit it. =A0N= ow fixing the problem is routine. =A0This grep command like this should fin= d it, and then you can remove it with vim or another text editor.
grep -n =3D\\s*$ *.sch
~Joshua


On 03/16/2012 08:54 PM, Thomas Oldbury wrote:
Trying to load a schematic into xgsch2pcb results in a blank PCB file.

Traced it down to a segfault here:

=A0$ gnetlist -q -g gsch2pcb -o FreeBox.new.pcb -m gnet-gsch2pcb-tmp.scm po= wer_main.sch
=A0Segmentation fault

I can delete a small section of my schematic and it goes away (generally ar= ound the lower optocoupler area); however, if I replace it and delete anoth= er section around the same area, it also goes away! Also, it seems (althoug= h it may just be me) that deleting parts individually doesn't work... y= ou have to delete all at once?! This has made trying to find an individuall= y faulty part hard, so I think it's probably some combination of factor= s that I'm unlucky enough to trip over.

I have attached my schematic in case it helps, it uses a few custom symbols= but the bug should still show up.

Is there a way for me to track down what part is causing the problem... nev= er had this before with gEDA.

Thanks,
Tom

--20cf30334f8f37b5b304bbd4a0b3--