Re: gnucap save prompt error

[patrick]

On Wed, Aug 26, 2020 at 1:20 PM Felix Salfelder <felix@salfelder.org> wrote:
>
> On Sun, Aug 23, 2020 at 12:18:20PM +0200, patrick wrote:
> > default plugins: cmake-4 2020.07.03
> > gnucap> save
> > file name?  abc.ckt
> > gnucap: /home/pmu/projects/gnucap/gnucap/lib/ap_construct.cc:125: CS&
> > CS::operator=(const string&): Assertion `!_file' failed.
>
> a wild guess
> ...
> +  assert(!is_file());

Thanks Felix. Yes, this works. InterestingI forgot to check the
declaration for the variable. I will keep this in mind.

> NB: I noticed that cmake does not either build in production nor in debug 
> mode.
> This is always suboptimal. In production mode, you would not have noticed the
> assertion (-DNDEBUG). and in debug mode, the "untested" would have appeared on
> the screen (-DTRACE_UNTESTED).
>

I am able to use gdb --args gnucap ... to see a stacktrace with some
symbols and file names in my CMake build. Probably the debug info you
mention is something else.
Regarding two release types, you mean to have a CMake variable set
like this https://stackoverflow.com/questions/7724569/debug-vs-release-in-cmake
?
Maybe I can try something out, but for now I am fine with my current build :)

By the way, what do you think would be important when loading
different MOS models in Gnucap, e.g. from here (I saw some notes in
the help mailing list on BSIM models as a plugin but not sure if still
valid):

http://bsim.berkeley.edu/models/