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

[Rik]

Update of bug #41699 (project octave):

                  Status:             In Progress => Confirmed              

    _______________________________________________________

Follow-up Comment #77:

Some progress, but the bug still remains.

Checking config.log, I see that OpenMP is detected and that there are lots of
instances of -fopenmp in the compilation step.

Installing in Windows and running Octave I can verify that


octave_config_info.features.OPENMP
ans =  1


But,


octave_config_info.CXXFLAGS
ans = -g -O2


I think this is because jwe modified the build process to put -pthreads and
-fopenmp somewhere else.  Checking XTRA_CXXFLAGS,


XTRA_CXXFLAGS = -pthread -fopenmp -mieee-fp


So this seems okay.

But the acid test still fails,


octave:1> x = imformats ()
warning: your version of GraphicsMagick limits images to 8 bits per pixel
warning: called from
    imformats>default_formats at line 256 column 11
    imformats at line 79 column 3
x =

  1x17 struct array containing the fields:

    coder
    ext
    isa
    info
    read
    write
    alpha
    description
    multipage

octave:2> exit

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


Looking at the compile log, the dldfcn __magick_read__.cc is definitely built
with -fopenmp.  Maybe we need to also build the graphics magick library with
-fopenmp?

I looked in the log file for the MXE build of graphicsmagick and I see


checking for i686-w64-mingw32-gcc -std=gnu99 option to support OpenMP...
unsupported


I'm going to try to rebuild graphicsmagick with John D's patch in place and
see if that helps.


    _______________________________________________________

Reply to this item at:

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

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