Mail Archives: geda-help/2012/03/22/10:16:05
--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 <Joshua DOT Lansford AT laserlinc DOT com>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<br><br>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.<br><br>Thanks for your help<br><br><div class=3D"gmail_quote">
On 22 March 2012 11:52, Joshua Lansford <span dir=3D"ltr"><<a href=3D"ma=
ilto:Joshua DOT Lansford AT laserlinc DOT com">Joshua DOT Lansford AT laserlinc DOT com</a>></=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
Hi Tom,<br>
=A0Was looking though the list and saw your request and it doesn't loo=
k like you have a response.<br>
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.<br>
grep -n =3D\\s*$ *.sch<span class=3D"HOEnZb"><font color=3D"#888888"><br>
~Joshua</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 03/16/2012 08:54 PM, Thomas Oldbury wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Trying to load a schematic into xgsch2pcb results in a blank PCB file.<br>
<br>
Traced it down to a segfault here:<br>
<br>
=A0$ gnetlist -q -g gsch2pcb -o FreeBox.new.pcb -m gnet-gsch2pcb-tmp.scm po=
wer_main.sch<br>
=A0Segmentation fault<br>
<br>
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.<br>
<br>
I have attached my schematic in case it helps, it uses a few custom symbols=
but the bug should still show up.<br>
<br>
Is there a way for me to track down what part is causing the problem... nev=
er had this before with gEDA.<br>
<br>
Thanks,<br>
Tom<br>
</blockquote>
</div></div></blockquote></div><br>
--20cf30334f8f37b5b304bbd4a0b3--
- Raw text -