Hi Neal,
this is not a drc2 bug, but a gnetlist one. I found where the problem
is, but I'm not a scheme guru, so I don't understand yet what is
happening.
The problem is in g_get_slots function, in g_netlist.c. There is a call
to scm_sort_list_x just before the function's end. This is where this
error is generated. I tried to just commenting out the call to
scm_sort_list_x, and gnetlist worked well.
The list passed to scm_sort_list_x is (1, 1).
Anyone knows what's the problem here?
Thanks,
Carlos
El sáb, 07-05-2005 a las 23:05 -0500, Neal Baer escribió:
 
I just compiled gEDA-2005080313, SuSE 9.2 yesterday.
I found what seems to be a bug with gnet-drc2.scm.  Creating a simple 
schematic of 2 resistors, having the same  reference (i.e. R1), same or 
different values, causes the DRC2 output as shown below.
I found the problem with a slotted part, thus each slot instance has the 
same reference designator.  This stops the DRC2 testing to complete, 
which deems it useless in this scenario.  I had to ensure that the 
reference numbers differ for the slotted parts to get DRC2 to complete 
its test.
Creating a netlist with the same reference numbers for slotted parts 
worked properly.
Any suggestions or workarounds?
Thanks,
Neal  
DRC OUTPUT OF TEST SCHEMATIC WITH DUPLICATE REFERENCES
   
nbaer@linux:~/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER> 
gnetlist -g drc2 test.sch -o -
gEDA/gnetlist version 20050313
gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more 
details.
This is free software, and you are welcome to redistribute it under 
certain
conditions; please see the COPYING file for more details.
Remember to check that your schematic has no errors using the drc2 
backend.
You can do it running 'gnetlist -g drc2 your_schematic.sch -o 
drc_output.txt'
and seeing the contents of the file drc_output.txt.
Loading schematic 
[/home/nbaer/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER/test.sch]
Checking non-numbered parts...
Checking duplicated references...
ERROR: Duplicated reference R1.
Checking nets with only one connection...
ERROR: Net has only one connected pin: dgnd
ERROR: Net has only one connected pin: unnamed_net1
Checking type of pins connected to a net...
Checking unconnected pins...
Checking slots...
Checking duplicated slots...
ERROR: In procedure apply:
ERROR: Wrong type argument in position 1: #<variable 80661b8 binding: 
#<primitive-procedure <>>
nbaer@linux:~/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER>       
     
---Publicidad--------------------------------------------------------
Alquila tu vehículo al mejor precio con HERTZ  
¡ 60 euros por el fin de semana !
http://tracker.tradedoubler.com/click?p=20846&a=1037797