[Octave-bug-tracker] [bug #40443] MinGW: Octave crashes on exit after GrahicksMagick tests

[Rik]

Follow-up Comment #23, bug #40443 (project octave):

I've narrowed it down to a simple one line function call.


octave-cli.exe
octave-cli.exe:1> imread ("x y z")
warning: your version of GraphicsMagick limits images to 8 bits per pixel
error: imread: cannot find x y z
error: called from:
error:   C:\Documents and Settings\Rik\My
Documents\Octave\octave-2013-11-26-18-45\share\octave\3.7.
7+\m\image\private\__imread__.m at line 56, column 5
error:   C:\Documents and Settings\Rik\My
Documents\Octave\octave-2013-11-26-18-45\share\octave\3.7.
7+\m\image\private\imageIO.m at line 64, column 26
error:   C:\Documents and Settings\Rik\My
Documents\Octave\octave-2013-11-26-18-45\share\octave\3.7.
7+\m\image\imread.m at line 107, column 30
octave-cli.exe:1> exit

panic: Segmentation violation -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete


Actually, I tested imread with a proper image file and it correctly reads the
file, but also segfaults when using exit.

It would seem that any command that initializes the GraphicsMagick library
eventually causes a segfault at exit.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?40443>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/