[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: gEDA user: gnetlist -gdrc buffer overflow and gnetlist -gspice-sdb killed
Hi again!
I have the following lines in my gnetlisrc:
(debug-options (list 'stack 200000))
(eval-options (list 'stack 200000))
Also, I tried with a bigger number and editing directly the
gnet-drc2.scm but the error still appearing. Reviewing my previous
flash converter (3 bits) I saw the same error but with the stack
options changed in the gnetlistrc all works fine.
Assuming that the drc2 backend will not report anything wrong, I tried
to run the spice-sdb backend but finished unexpectedly with 'Killed'.
The output and the content of the gnetlist.log:
- using spice-sdb: [3][1]http://pastebin.com/MpWjqVq8
- gnetlist.log: [2]http://pastebin.com/qumXeXbu
I'm using several files for each component because my thesis work is
related to a fail that is injected on MOS transistors and I need to
attach a voltage source in one and only one transistor at a time. I
made a script that read the netlist file generated by spice-sdb backend
and insert the voltage source on each transistor one per one and
simulates with ngspice but now I can't make the netlist. Due this I
can't have one "model file" for my parts (as I tried some time ago when
I start with the project) because if I insert a fail (voltage source)
on a model file all instances of the components using that model file
will have the fail at the same time.
I'm very confused. I'll keep trying.
Thanks!
On Sun, Feb 28, 2010 at 1:44 PM, al davis <[3]ad252@xxxxxxxxxxxxxxxx>
wrote:
On Sunday 28 February 2010, John Doty wrote:
> Ah, but it has an open interface we can use. A great strength
> of gEDA is that the tools play well with other tools,
> whether they are part of gEDA or not.
I don't care how many proprietary tools you can leverage by
starting the schematic on gschem.
I do care how much of a design you can do with a 100% free/open-
source flow, and how well that kind of flow works.
I do care about a migration path to encourage people to move
from proprietary flows to free/open-source flows.
I do care about cooperation between free/open-source tools,
whether they are part of gEDA or not.
I do care about welcoming those who are making free/open-source
tools, adding to how much of a design you can do with a 100%
free/open-source flow, whether they are part of gEDA or not.
I do care about welcoming researchers, who are creating the new
state of the art, the tools of the future.
I do care about welcoming hobbyists, who are creating our
culture and future.
_______________________________________________
geda-user mailing list
[4]geda-user@xxxxxxxxxxxxxx
[5]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
--
Facundo J Ferrer
References
1. http://pastebin.com/MpWjqVq8
2. http://pastebin.com/qumXeXbu
3. mailto:ad252@xxxxxxxxxxxxxxxx
4. mailto:geda-user@xxxxxxxxxxxxxx
5. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user