Odd behavior when shorting nets in a lower hierarchy sch

Bug #698395 reported by ahvezda
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gEDA
Fix Released
High
Unassigned

Bug Description

If I make a subnet, with a bunch of components in it,
it seems to work alright. However, I also tried to make
a 2-pin subnet containing only a short-circuit. This
connection was completely ignored by gnetlist!!
(originally reported by Arvid Rosén)

Attached are the schematics and symbol.

Here is the output from gnetlist -g geda top.sch
unnamed_net9 : Rload 1, Rtop4 1, Rtop2 2
GND : Rload 2, Vin 2
unnamed_net8 : Rtop3 2, Rtop1 1, Vin 1
unnamed_net4 : Utest/R34 1, Rtop3 1
unnamed_net3 : Utest/R34 2, Rtop4 2
unnamed_net2 : Rtop1 2
unnamed_net1 : Rtop2 1

Ideally the last two nets should be shorted, however
gnetlist is ignoring the net connecting the two in -
out symbols in test.sym.

The workaround is use a zero ohm resistor.

Revision history for this message
ahvezda (ahvezda-users) wrote :
Revision history for this message
ahvezda (ahvezda-users) wrote :
Revision history for this message
ahvezda (ahvezda-users) wrote :
Revision history for this message
ahvezda (ahvezda-users) wrote :
Revision history for this message
Krzysztof Kościuszkiewicz (k-kosciuszkiewicz) wrote :

I can still reproduce this in 1.7.0

Changed in geda:
status: New → Confirmed
importance: Undecided → Medium
Changed in geda:
importance: Medium → High
Changed in geda:
status: Confirmed → Fix Committed
Peter TB Brett (peter-b)
Changed in geda:
milestone: none → 1.7.1
Peter TB Brett (peter-b)
Changed in geda:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.