Hi Diego, Le mardi 02 novembre 2021 à 14:16 +0100, Diego Zuccato a écrit : > I currently used a different workaround: I installed the single-thread > libopenblas and that enables the coexistence of cdo and octave.
So it seems that your problem is somehow related to multithreading (with pthread) in openblas. However I fail to understand the relationship with cdo. Could you please expand on that? > Session transcipt where I test current configuration, install the > multithreaded version, test the segfault then recover the previous state: 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. 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) Is there something special in /usr/local? Is the segfault triggered by some computation? In particular, is there something in your ~/.octaverc, ~/.config/octave/octaverc or /etc/octaverc? Is the result different if your run “octave-cli” instead of “octave” (to disable the GUI)? Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
