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

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

[Octave-bug-tracker] [bug #58957] [octave forge] (sparsersb) Failure to


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #58957] [octave forge] (sparsersb) Failure to install and crash in function
Date: Tue, 22 Sep 2020 12:59:38 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36 Edg/85.0.564.51

Follow-up Comment #37, bug #58957 (project octave):

Sorry, I'm not sure I understand what I am supposed to do.
I cross-built Octave with all its dependencies (including librsb) for Windows
on Linux with MXE Octave.
MXE Octave cleans up the build directories of each package it has built. I no
longer have a librsb build directory.
Instead, I have an msys2 environment with installed gcc and librsb. That is
the same librsb that Octave is using.
So, I ran the following at the msys2 shell:

$ gcc rsb_mtx_rndr.c -otest.exe -lrsb -fopenmp
$ gdb test.exe
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from test.exe...
(gdb) r
Starting program: D:\SVN\Octave\bug58957\test.exe
[New Thread 23092.0x2fe4]
[New Thread 23092.0x590]
[New Thread 23092.0x4d50]
[New Thread 23092.0x3f74]
[New Thread 23092.0x15dc]
[New Thread 23092.0xde4]
OK
[Thread 23092.0xde4 exited with code 0]
[Thread 23092.0x15dc exited with code 0]


Is this a meaningful test? In case it is: The test program didn't crash.
I ran the program about 20-30 times but it never crashed.

I am attaching the "crash.eps" file that was created by that program in case
that helps.

One difference is that this test program was built natively on Windows.
"sparsersb" was cross-built on Linux for Windows.
To test if that makes a difference, I re-built and re-installed sparsersb on
Windows. In Octave:

>> pkg install -forge sparsersb
warning: LFLAGS is deprecated and will be removed in a future version of
Octave, use LDFLAGS instead
For information about changes from previous versions of the sparsersb package,
run 'news sparsersb'.
>> pkg load sparsersb
>> pkg list
[...]
          sparsersb *|   1.0.8 | C:\Users\Markus\octave\sparsersb-1.0.8
[...]
>> sparsersb(sparsersb([1]),"render", "crash.eps" ,1024);


But Octave crashed on the last command.

(file #49838)
    _______________________________________________________

Additional Item Attachment:

File name: crash.eps                      Size:2 KB
    <https://file.savannah.gnu.org/file/crash.eps?file_id=49838>



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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