[Octave-bug-tracker] [bug #41699] imread causes a segmentation fault when exiting Octave

[Ian Journeaux]

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

Here is what I tried on my Windows 7 machine

1. Open up a command window
2. Set OMP_NUM_THREADS=1
3. run Octave-cli.exe
4. test imread
5. exit(0)

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

I also tried running Octave-cli with GDB (no debug info though)
and got 

Program received signal SIGSEGV, Segmentation fault.
0x68821aa0 in liboctinterp-2!_ZN5ArrayIdED2Ev ()
   from C:OctaveOctave-3.8.1binliboctinterp-2.dll

I wonder if GraphicsMagick under windows actually uses the OMP_NUM_THREADS=1
environment variable

I can install the debug version of the different DLLs if that would be useful

    _______________________________________________________

Reply to this item at:

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

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