Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-05 Thread Diego Zuccato
Hello Sébastien. I think it's quite important to have it fixed in stable since it's quite tricky to debug and results in an error while installing or upgrading octave. Does that qualify as a major impact? :) Tks. Il 05/11/2021 14:35, Sébastien Villemot ha scritto: Control: retitle -1 segfau

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-05 Thread Sébastien Villemot
Control: severity -1 important Le vendredi 05 novembre 2021 à 15:00 +0100, Diego Zuccato a écrit : > I think it's quite important to have it fixed in stable since it's quite > tricky to debug and results in an error while installing or upgrading > octave. Does that qualify as a major impact? :)

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-05 Thread Sébastien Villemot
Control: retitle -1 segfault when running out of memory Control: tags -1 = upstream fixed-upstream Dear Diego, Le vendredi 05 novembre 2021 à 06:34 +0100, Diego Zuccato a écrit : > Il 04/11/2021 12:27, Sébastien Villemot ha scritto: > > > I happen to have access to a machine with exactly the sam

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-04 Thread Diego Zuccato
Il 04/11/2021 12:27, Sébastien Villemot ha scritto: 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.Uhm...

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-04 Thread Diego Zuccato
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 dependenc

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-04 Thread Sébastien Villemot
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)

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-02 Thread Diego Zuccato
Hi Sébastien. I currently used a different workaround: I installed the single-thread libopenblas and that enables the coexistence of cdo and octave. Session transcipt where I test current configuration, install the multithreaded version, test the segfault then recover the previous state: -8<

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-11-02 Thread Sébastien Villemot
Control: reassign -1 libopenblas0 0.3.13+ds-3 Control: tags -1 + moreinfo Dear Diego, Le vendredi 08 octobre 2021 à 09:04 +0200, Diego Zuccato a écrit : > Continuing a triage, I noticed that removing cdo and its dependencies > (including libopenblas0) and reinstalling octave got rid of the > se

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-10-08 Thread Diego Zuccato
Hello. Just an update. Continuing a triage, I noticed that removing cdo and its dependencies (including libopenblas0) and reinstalling octave got rid of the segfault. Reinstalling cdo reintroduced the segfault. The updated backtrace (I used the wrong executable, sorry) is: GNU gdb (Debian 10.1

Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)

2021-10-01 Thread Diego Zuccato
Package: octave Version: 6.2.0-1 Severity: normal Dear Maintainer, * What led up to the situation? Upgrade from Buster to Bullseye * What exactly did you do (or not do) that was effective (or ineffective)? Tried removing/purging and reinstalling octave and many dependencies. When I re