revision1.net -> the netlist of the affected circuit
revision1.sch -> the (gschem) schematic of the affected circuit.
ngspice.revision1.log -> the terminal output of the ngspice session
1) load ngspice -> `ngspice revision1.net`
2) run transient analysis -> `tran 0.1m 10m`
3) program hangs; ^C does not interrupt analysis
4) trace syscalls -> `dtruss -f ngspice revision1.net > ngspice.revision1.log`
5) run transient analysis -> `tran 0.1m 10m`
6) ^C to kill dtruss/ngspice when ngspice hangs
At the end of the log file, there are 14 lines, all syscalls to gettimeofday(). These 14 lines were repeated many, many times. I removed the repeats for clarity. Other than that, the only modification I made was removing personal data from the log.
I understand that my circuit may be malformed, and that this may be the expected behavior, but it seems reasonable to expect ngspice to do something, including responding to ^C like a transient analysis normally does.
Log in to post a comment.