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

[Mike Miller]

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

I'm also unsure under what conditions this is triggered. For example, on Linux
running "test imread" does not cause the error on exit. All I can say it seems
to be due to GraphicsMagick using OpenMP, at least on my Linux distribution,
I'm not sure if that's the case using MXE. I also only see the segfault when
running octave in gdb.

The thing that led me to look into OpenMP was that gdb showed new threads
starting when I called imread to open your tif file. I knew that Octave would
not be starting those threads, so it looked like it was internal to
GraphicsMagick.

So my questions are, does GraphicsMagick built in MXE use OpenMP (built with
gcc -fopenmp and/or linked with libgomp)? Are threads observed to start when
calling certain im* functions in Octave? Is libgomp available in the MXE gcc
environment? Does gcc -fopenmp work as expected when building things in MXE?
Is --enable-openmp expected to work for Octave in MXE? Are the resulting
octave libraries and executables linked with libgomp? If GraphicsMagick is and
Octave isn't, then what else is needed to link Octave with libgomp, and if
that is done, does it fix the error?

    _______________________________________________________

Reply to this item at:

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

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