Re: Seg Fault

Markus Mützel <[email protected]>
Newsgroups gmane.comp.gnu.octave.general
Message-ID <trinity-ee7b3e7c-9964-4e0d-8cf3-36ee815e0fd0-1621099983765@3c-app-gmx-bap65>
Am 15. Mai 2021 um 19:20 Uhr schrieb "Mike Miller":
> Markus Mützel:
> > Did you recently update to a newer Octave version?
> > In that case, it's necessary to re-compile the binaries that are part of any installed package. That might explain why it is no longer crashing after "pkg uninstall" and "pkg install -forge".
> 
> That seems like a problem for a stable bug fix update. It's usually
> expected that oct files compiled for Octave version 6.1 will still
> work with version 6.x without recompiling.

I agree.
It's not clear to me which version the OP updated from (or if they updated at all). I was assuming they updated from a version prior to Octave 6.x.
Binaries compiled with an older major version of Octave are probably not expected to work in a newer (major) version (and vice versa). Is a segfault the expected behavior though?

IIRC, starting with Octave 7, package binaries will be installed in paths that depend on the major version number by default. So that error might be somewhat mitigated in the future.

Markus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.