gEDA-bug: [Bug 698395] Re: Odd behavior when shorting nets in a lower hierarchy sch

[Krzysztof KoÅciuszkiewicz <698395@xxxxxxxxxxxxxxxxxx>]

I can still reproduce this in 1.7.0

** Changed in: geda
       Status: New => Confirmed

** Changed in: geda
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/698395

Title:
  Odd behavior when shorting nets in a lower hierarchy sch

Status in GPL Electronic Design Automation tools:
  Confirmed

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.




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