[Octave-bug-tracker] [bug #41699] imformats causes a segmentation fault on Windows when Octave exits

[Rik]

Follow-up Comment #110, bug #41699 (project octave):

I've added bug #41074 as a dependency.  This was the original report that
motivated the use of a vbs file.  Basically, we'll have a minimized command
window in the taskbar if we change the shortcut not to use the vbs file.

@John: You want to change to running octave.exe --force-gui directly, rather
than just octave-gui.exe.  I also changed my desktop shortcut to start in the
$OCTAVE/bin directory.  With these changes I can run any of the problem code
in this bug report repeatedly on a Windows XP VM.

@jwe: Running your test code with 4.0.2 produces this for me


>> imwrite (randi (255, 100, 100), "foo.tif");
>> clear all
>> imwrite (randi (255, 100, 100), "foo.tif");
warning: your version of GraphicsMagick limits images to 8 bits per pixel
warning: called from
    __imwrite__ at line 201 column 3
    imwrite at line 111 column 5


What may be significant is the warning.  Normally the code just segfaults so
it is possible that what is happening is that the warning/exception handling
mechanism is creating problems.  Or it could be a red herring.


    _______________________________________________________

Reply to this item at:

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

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