Re: [ng-spice] Rework 9 - configure problems
For what its worth,...
In response to the recent topic of memory leaks:
I discovered an interesting "leak" that I would fix but
I think its root cause is a larger problem than I can
address by myself. It started with a seg-fault (what
doesn't?),...
The cause was from an improperly formatted input file.
I cut-and-pasted the input data from a data sheet *.pdf and
some of the spaces between node names and node numbers
got lost, creating what to the program (probably) looked
like a node name with a single node number. This was then
acted upon and some where we obviously exceeded a memory
boundary. While I am not familiar with the spice input file
specification I can see that a node name should be able
to have a single node number. The problem then I guess is
how to detect-and-warn when this might be a mistake and not
by design. Some kind of reality check on the input file.
This type of check might already exist in the spice code
and just missed my example, I don't know. There are probably
more important issues than this but it seemed to be related
(ie. could be misinterpreted as a memory leak).
Best reagrds
cinbody
Partial thread listing: