Process 11813 stopped
* thread #23, stop reason = EXC_BAD_ACCESS (code=1, address=0x1c0)
frame #0: 0x00000001104c65ad
libngspice.0.dylib`MIFsetup(matrix=<unavailable>,
inModel=<unavailable>, ckt=<unavailable>, states=<unavailable>) at
mifsetup.c:148:32 [opt]
145 if(model->param[i]->is_null) {
146
147 /* setup a pointer for quick access */
-> 148 param_info = &(DEVices[mod_type]->DEVpublic.param[i]);
149
150 /* determine the size and allocate the
parameter element(s) */
151 if(! param_info->is_array) {
Target 0: (kicad) stopped.
For laser_driver:
Process 12905 stopped
* thread #22, stop reason = EXC_BAD_ACCESS (code=1, address=0x1c0)
frame #0: 0x000000011d3b25ad
libngspice.0.dylib`MIFsetup(matrix=<unavailable>,
inModel=<unavailable>, ckt=<unavailable>, states=<unavailable>) at
mifsetup.c:148:32 [opt]
145 if(model->param[i]->is_null) {
146
147 /* setup a pointer for quick access */
-> 148 param_info = &(DEVices[mod_type]->DEVpublic.param[i]);
149
150 /* determine the size and allocate the
parameter element(s) */
151 if(! param_info->is_array) {
Target 0: (kicad) stopped.
Is this helpful?
On Tue, Sep 17, 2019 at 9:52 AM Holger Vogt <email address hidden> wrote:
>
> We have:
>
> Thread 10 Crashed:
> 0 libngspice.0.dylib 0x000000011f6d4c5d MIFsetup + 109
> 1 libngspice.0.dylib 0x000000012b3da3d6 CKTsetup + 214
> 2 libngspice.0.dylib 0x000000012b3d41b1 CKTdoJob + 961
>
> What I will do next to figure out where exactly in function MIFsetup of
> file mifsetup.c the crash is happening:
>
> Start eeschema
> load sallen-key project
> Select Tools-->Simulator
>
> *start debugger in terminal
>
> lldb
>
> *attach debugger lldb to process
>
> process attach --name eeschema
>
> * in eeschema simulator window
> Start Simulation
>
> *in terminal watch debugger output
> Hopefully it crashes and tells me where the crash happened and what is causing the crash.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835296
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1835296/+subscriptions
This is for sallen_key:
Process 11813 stopped 0.dylib` MIFsetup( matrix= <unavailable> , <unavailable> , ckt=<unavailable>, states= <unavailable> ) at >param[ i]->is_ null) { mod_type] ->DEVpublic. param[i] ); >is_array) {
* thread #23, stop reason = EXC_BAD_ACCESS (code=1, address=0x1c0)
frame #0: 0x00000001104c65ad
libngspice.
inModel=
mifsetup.c:148:32 [opt]
145 if(model-
146
147 /* setup a pointer for quick access */
-> 148 param_info = &(DEVices[
149
150 /* determine the size and allocate the
parameter element(s) */
151 if(! param_info-
Target 0: (kicad) stopped.
For laser_driver:
Process 12905 stopped 0.dylib` MIFsetup( matrix= <unavailable> , <unavailable> , ckt=<unavailable>, states= <unavailable> ) at >param[ i]->is_ null) { mod_type] ->DEVpublic. param[i] ); >is_array) {
* thread #22, stop reason = EXC_BAD_ACCESS (code=1, address=0x1c0)
frame #0: 0x000000011d3b25ad
libngspice.
inModel=
mifsetup.c:148:32 [opt]
145 if(model-
146
147 /* setup a pointer for quick access */
-> 148 param_info = &(DEVices[
149
150 /* determine the size and allocate the
parameter element(s) */
151 if(! param_info-
Target 0: (kicad) stopped.
Is this helpful?
On Tue, Sep 17, 2019 at 9:52 AM Holger Vogt <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1835296 /bugs.launchpad .net/kicad/ +bug/1835296/ +subscriptions
>
> We have:
>
> Thread 10 Crashed:
> 0 libngspice.0.dylib 0x000000011f6d4c5d MIFsetup + 109
> 1 libngspice.0.dylib 0x000000012b3da3d6 CKTsetup + 214
> 2 libngspice.0.dylib 0x000000012b3d41b1 CKTdoJob + 961
>
> What I will do next to figure out where exactly in function MIFsetup of
> file mifsetup.c the crash is happening:
>
> Start eeschema
> load sallen-key project
> Select Tools-->Simulator
>
> *start debugger in terminal
>
> lldb
>
> *attach debugger lldb to process
>
> process attach --name eeschema
>
> * in eeschema simulator window
> Start Simulation
>
> *in terminal watch debugger output
> Hopefully it crashes and tells me where the crash happened and what is causing the crash.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https:/