From: hreba <f_hreba@yahoo.com.br>
Subject: Re: generic provokes segmentation fault
Date: Mon, 18 May 2020 22:16:20 +0200
Date: 2020-05-18T22:16:20+02:00 [thread overview]
Message-ID: <hig8olFrhghU1@mid.individual.net> (raw)
In-Reply-To: <r9tvh9$1l2u$1@gioia.aioe.org>
On 2020-05-18 14:36, Dmitry A. Kazakov wrote:
> What is global variables you are talking about? gsl_odeiv2_driver seems
> to be allocated and initialized using library functions.
Initially, I tried the following:
- the library defines a type with that driver as a private component
- the client declares a variable of that type
- the client calls the library's initialization function, which
instanciates this variable (and the driver within)
I just was not able to get around that local/non-local object/pointer
problem, and for now the driver is a global variable hidden in the
library, initialized as a side effect of Init_Solve, as a workaround.
This is unsatisfactory of course, because only 1 driver can be active at
a time. Presently, I use flags to ensure initialization and to prevent
multiple ones. In order not to mix topics, and to avoid posting lots of
code here, I would like to come back on this later, with a minimal example.
Regards,
--
Frank Hrebabetzky, Kronach +49 / 9261 / 950 0565
next prev parent reply other threads:[~2020-05-18 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 14:19 generic provokes segmentation fault hreba
2020-05-17 17:51 ` Dennis Lee Bieber
2020-05-17 18:34 ` Dmitry A. Kazakov
2020-05-18 11:29 ` hreba
2020-05-18 12:36 ` Dmitry A. Kazakov
2020-05-18 20:16 ` hreba [this message]
2020-05-18 21:30 ` Dmitry A. Kazakov
2020-05-17 21:02 ` Jeffrey R. Carter
2020-05-18 20:21 ` hreba
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox