|
From: | Julien Bect |
Subject: | Re: Octave crashes on old MEX-files: how can I detect/prevent this? |
Date: | Wed, 7 Dec 2016 08:50:00 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 |
Le 06/12/2016 à 19:33, Mike Miller a écrit :
On Tue, Dec 06, 2016 at 09:58:30 +0100, Julien Bect wrote:But Kai's solution really solves my problem, by providing a mean to detect that the MEX-file must be recompiled.I guess my claim is that it is not a guaranteed hack. I think it is only because your mex file is loading a different liboctinterp into the same Octave process space, that *something* is being corrupted in memory, and there is no guarantee that the error you are seeing is reliable or meaningful in any way, other than "Octave is screwed up now".
Ok I get it. Thanks for the clarification. But isn't this a serious problem for Octave users ? What about installed packages, when a user upgrades from 4.0.2 to 4.2.0 ? (perhaps should we move this discussion to the maintainers list now ?)
[Prev in Thread] | Current Thread | [Next in Thread] |