octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62144] Crash on exit using OpenBlas built wit


From: Arun Giridhar
Subject: [Octave-bug-tracker] [bug #62144] Crash on exit using OpenBlas built with USE_TLS=1 but not an Octave bug
Date: Sun, 6 Mar 2022 11:29:41 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?62144>

                 Summary: Crash on exit using OpenBlas built with USE_TLS=1
but not an Octave bug
                 Project: GNU Octave
            Submitted by: arungiridhar
            Submitted on: Sun 06 Mar 2022 11:29:40 AM EST
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Segfault, Bus Error, etc.
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

This is a near-repeat of bug #61742 that I am adding here to get a bug number
so I can report upstream to OpenBlas. The previous bug was for OpenBlas 0.3.19
and this one is for OpenBlas 0.3.20.

This is not an Octave bug and no action is needed from Octave devs.

There is a crash on exiting Octave when using OpenBlas built with the
USE_TLS=1 flag that comes standard with some Linux distros like Arch, Manjaro
and other Arch derivatives.

The test is as follows, when using multithreaded OpenBlas:


$ octave
octave:1> n = 64; A = ones(n,n); B = A^2; assert (all (B(:) == n))
octave:2> exit
### This will exit normally in all circumstances, because multithreading is
not used for n <= 64

$ octave
octave:1> n = 65; A = ones(n,n); B = A^2; assert (all (B(:) == n))
octave:2> exit
### This will crash with a segfault if USE_TLS=1 was used in building
OpenBlas, and exit normally otherwise


No action is needed from the Octave dev team. I will be submitting a bug
report upstream to OpenBlas linking to this report.

The solution as before is to not use USE_TLS=1 for OpenBlas, or if your
distro's OpenBlas PKGBUILD installation script already comes with it, to
change it to USE_TLS=0. This package still uses the problematic USE_TLS=1
setting as of now: https://aur.archlinux.org/packages/openblas-lapack/





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62144>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]