Re: gEDA-user: gnetlist segmentation fault

[kai-martin knaak <kmk@xxxxxxxxxxxxxxx>]

Thomas Dean wrote:

> I have an application which causes a seg fault in gnetlist.  I think
> this can be fixed by changing the schematic. 

The offending symbol is A103 which refers to spice-include-1.sym
The symbol  contains a spurious attribute "netname=" with no value.


> But, Segmentation fault is NEVER the proper response.

The gsch2pcb back-end does not segfault but fails with:
     At least gnetlist 20030901 is required for m4-xxx options.
Looks like this is another incarnation of the infamous m4 parsing 
failure, that has been haunting geda users for years now.

> ====ulf-ant.sch=============================
> v 20100214 2
> C 19500 47500 1 0 0 lf353-1.sym
> {
(...)
>
> T 24300 45700 9 10 1 0 0 0 1
> 100 ft. Twisted Pair (CAT-5)
> C 20500 49700 1 0 0 spice-include-1.sym
> {
> T 20600 50100 5 10 1 1 0 0 1
> refdes=A102
> T 21000 49800 5 10 1 1 0 0 1
> file=ad797.cir
> T 20500 49700 5 10 1 0 0 0 1
> netname=
> }
(...) 

I guess, the "=" at the end of the string is the trigger. If the 
attribute contains just a single letter, gnetlist is happy with the 
file. How did you manage to add the empty netlist attribute? IMHO, the 
attribute editor in the GUI ties to prevent empty string values.

Bottom line: The gnetlist really needs to be more fussy on the syntax. 
Currently it seems to assume m4 where there isn't. In addition, m4 
should fail gracefully rather than returning broken strings. 

---<)kaimartin(>---
-- 
Kai-Martin Knaak
Öffentlicher PGP-Schlüssel:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53



_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user