[Octave-bug-tracker] [bug #64446] Sparse QR segfaults with SuiteSparse 7 on 32-bit architectures

[Sébastien Villemot]

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

                 Summary: Sparse QR segfaults with SuiteSparse 7 on 32-bit
architectures
                   Group: GNU Octave
               Submitter: svillemot
               Submitted: mer. 19 juil. 2023 07:05:47
                Category: Octave Function
                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: 8.2.0 8.X Series Bug Fix Release 
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: mer. 19 juil. 2023 07:05:47    By: Sébastien Villemot <svillemot>
Debian is currently transitioning to SuiteSparse 7, and the Octave 8.2.0
testsuite now fails on 32-bit architectures.
See for example:
https://buildd.debian.org/status/fetch.php?pkg=octave&arch=i386&ver=8.2.0-4&stamp=1689712650&file=log

More precisely, there is now a segmentation fault in the tests for the
“qr” function. The segfault is triggered at line 523 of
liboctave/numeric/sparse-qr.cc. I attach a backtrace obtained by running
“test qr” on i386.

Note that in Debian, Octave 8.2.0 has been patched to compile against
SuiteSparse 7 (hg ID 134152cf1a3f has been backported).

I tried to reproduce the problem on the default branch, but unfortunately that
branch fails to build on i386 for an unrelated reason (some issue around
time_t types).

Note that between SuiteSparse 5 and 7, the SuiteSparse_long type has changed
on 32-bit architectures. It used to be a long (i.e. 32-bit), and it is now an
int64_t (i.e. 64-bit). I don’t know if that is related to the issue. There
is however already some code in sparse-qr.cc to deal with the different
possible sizes of SuiteSparse_long, so maybe this is a red herring.








    _______________________________________________________
File Attachments:


-------------------------------------------------------
Date: mer. 19 juil. 2023 07:05:47  Name: suitesparse7.log  Size: 18kio   By:
svillemot

<http://savannah.gnu.org/bugs/download.php?file_id=54939>

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Message posté via Savannah
https://savannah.gnu.org/