Re: [ng-spice-devel] bugs


To ng-spice-devel@ieee.ing.uniroma1.it
From Alan Gillespie <alan.gillespie@analog.com>
Date Wed, 27 Sep 2000 13:52:53 -0400
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
References <20000927184605.A27105@cgmd80028.chello.nl >
Reply-To ng-spice-devel@ieee.ing.uniroma1.it
Sender agillesp@epc.co.uk

Thanks, Arno.

Does that mean that segment fault I got during my debug
session was probably not the same one that was crashing
the program in "real life". I haven't got the code here, but I
do remember seeing stuff that made me think that "signals"
were being trapped. What you're saying explains that.

But when I run ngspice in batch mode with a rawfile, or
if I run in interactive mode but I run with "run rawfile" to
dump the data to a rawfile during the run, I get a segment
fault.

I suspect that you guys don't run it in this way. Is that
true ? Is there a way to save to a rawfile after the simulation
has finished. (My manual's at home in Scotland, and the
help system didn't seem to work, even after I corrected
the help directory name).

I'm sure there is a way to do this, and I also think that
this uses different rawfile writing routines. This might
explain why you haven't had trouble with my changes
in outitf.c  I think the data format changes only work
if you're dumping data after every simulation step.
This also implies that the segfault is occuring in those
routines.

Cheers,

Alan



Partial thread listing: