Il 04/11/2021 12:27, Sébastien Villemot ha scritto:
So it seems that your problem is somehow related to multithreading
(with pthread) in openblas.
Exactly.
However I fail to understand the relationship with cdo. Could you
please expand on that?
cdo installed libopenblas-pthread as a dependency, and that broke octave.
I happen to have access to a machine with exactly the same CPU (and
Debian Bullseye). I fail to replicate your problem there. I can start
octave with libopenblas0-pthread and there is no segfault.
So there must be another factor at play.
Possible. That's a system that got upgraded many times (started as a
Debian 6.0, IIRC!)
Do you confirm that octave and all its dependencies are pristine Debian
packages from Debian Bullseye? (and not binaries compiled by yourself
or packages obtained from another suite)
Yes. Till yesterday, the only packages not from Debian official repos
were the PBIS ones (today I added Glusterfs repos).
Is there something special in /usr/local?
Nothing except pbis-open and some python scripts.
Is the segfault triggered by some computation? In particular, is there
something in your ~/.octaverc, ~/.config/octave/octaverc or
/etc/octaverc?
No. Just trying to run octave from a new user triggers the error.
Is the result different if your run “octave-cli” instead of “octave”
(to disable the GUI)?
No.
Not using octave myself, I noticed it because apt failed during the last
dist-upgrade, and it uses octave-cli .
--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
