2005-05-26 21:29:52 +02:00
|
|
|
This file contains a list of known but not yet fixed bugs in ngspice.
|
2004-09-04 11:58:39 +02:00
|
|
|
===========================================================================
|
2001-12-07 15:59:49 +01:00
|
|
|
|
2005-08-23 20:54:22 +02:00
|
|
|
How to submit a bug report:
|
|
|
|
|
|
|
|
|
|
There are three ways to report a bug you have discovered in ngspice:
|
|
|
|
|
|
|
|
|
|
* Bug tracker: This is the preferred method of reporting a bug.
|
|
|
|
|
Using the tracker on Sourceforge.ner site will make your report
|
|
|
|
|
open by everyone and the chances of finding a fix will increase.
|
|
|
|
|
|
|
|
|
|
* ngspice-bugs list: If you have used ngspice, you probably noticed
|
|
|
|
|
that the banner that appears when ngspice starts says that you can
|
|
|
|
|
send bug reports to the ngspice-bugs@lists.sourceforge.net address.
|
|
|
|
|
This is the address of a mailing list dedicated to receive bug reports.
|
|
|
|
|
|
|
|
|
|
* ngspice-devel list: If you are a member of this list, you can write
|
|
|
|
|
directly to the developers' list. Do not subscribe to the list only
|
|
|
|
|
for sending bug reports.
|
|
|
|
|
|
|
|
|
|
Before sending a bug report please note: all information you send to the bug
|
|
|
|
|
tracking system or on the mailing lists is public. If you need to send
|
|
|
|
|
sensitive information, send them to a developer directly but still write non
|
|
|
|
|
sensitive data on the bug tracking system to keep track of bug history.
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
OPEN BUGS:
|
|
|
|
|
------------------------------------------------------------------------------
|
2004-09-04 11:58:39 +02:00
|
|
|
* return value:
|
|
|
|
|
|
|
|
|
|
When ngspice is called in batch mode it returns 1 even if the simulations
|
|
|
|
|
are run. The problem arise when there is a .control section but no
|
|
|
|
|
.print, .plot or .fourier lines. Ngspice outputs:
|
|
|
|
|
|
|
|
|
|
Note: No ".plot", ".print", or ".fourier" lines; no simulations run
|
|
|
|
|
|
|
|
|
|
and exits returning 1.
|
|
|
|
|
|
|
|
|
|
Workaround: add -r <dummyfile> to the command line to avoid this.
|
