[Octave-bug-tracker] [bug #59206] crash during matrix multiplication (Win only)

[Markus Mützel]

Update of bug #59206 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

I can reproduce the crash with 6.0.90 using OpenBLAS.
gdb backtrace from the crash:

Thread 5 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 19580.0x4474]
0x0000000001de00ee in libopenblas!dcabs1_ ()
   from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\bin\libblas.dll
(gdb) bt
#0  0x0000000001de00ee in libopenblas!dcabs1_ ()
   from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\bin\libblas.dll
#1  0x00000000010f61d5 in zgemm3m_ ()
   from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\bin\libblas.dll
#2  0x000000000124c534 in openblas_get_parallel_ ()
   from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\bin\libblas.dll
#3  0x00007ff8baeb6fd4 in KERNEL32!BaseThreadInitThunk ()
   from C:\WINDOWS\System32\kernel32.dll
#4  0x00007ff8bcd5cec1 in ntdll!RtlUserThreadStart ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
#5  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)


The crash doesn't happen with reference BLAS.

I cannot reproduce with a build from stable hg id 7778bc023114 with MXE Octave
hg id e2582a427c2a. The same for reference BLAS and OpenBLAS.

The only change to the OpenBLAS build rule in MXE Octave after the release
candidate was this one:
https://hg.octave.org/mxe-octave/rev/c475092f8142
openblas: Support using ccache.

But I don't see how that could have any influence.

Could the updated binutils have fixed this?
https://hg.octave.org/mxe-octave/rev/bc8ef5fda77b
src/build-binutils.mk, src/native-binutils.mk: update to v2.35.1

    _______________________________________________________

Reply to this item at:

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

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