Opened 5 years ago

Closed 5 years ago

#58693 closed defect (fixed)

GraphicsMagick @1.3.32: gm identify crashes

Reported by: nir-krakauer Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Port: GraphicsMagick

Description

With the new GraphicsMagick version 1.3.32, installing the default Octave (as octave-5.1.0_0+accelerate+app+docs+gfortran+graphicsmagick+qt5+sound+sundials.darwin_15.x86_64.tbz2 ) results in a crash when Octave is run and, for example, the imformats command is invoked:

octave:1> imformats
  fatal: caught signal Abort trap: 6 -- stopping myself...
  Abort trap: 6

This appears to be due to the Octave binary being built with an old GraphicsMagick library version:

otool -L /opt/local/lib/octave/5.1.0/liboctinterp.7.dylib | grep Magic
	/opt/local/lib/libGraphicsMagick++.12.dylib (compatibility version 17.0.0, current version 17.0.0)
	/opt/local/lib/libGraphicsMagick.3.dylib (compatibility version 23.0.0, current version 23.0.0)

otool -L /opt/local/bin/gm | grep Magick
	/opt/local/lib/libGraphicsMagick.3.dylib (compatibility version 24.0.0, current version 24.0.0)

The problem is fixed after downgrading GraphicsMagick to the previous version (1.3.31) using a local Portfile and then reinstalling Octave.

Attachments (1)

octave-gui_2019-07-07-125936_MacBook.crash (60.3 KB) - added by nir-krakauer 5 years ago.
Crash log

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign added

libGraphicsMagick's major version number (3) hasn't changed, which should mean that the new version is compatible with the old one.

Can you attach the crash log file (from inside ~/Library/Logs/DiagnosticReports/)?

Does the crash go away if you rebuild octave from source, now that the new libGraphicsMagick is installed? (I would not expect it to.)

Changed 5 years ago by nir-krakauer

Crash log

comment:2 Changed 5 years ago by nir-krakauer

I wasn't successful in building octave from source because the build dependency clang-5.0 had a build error.

comment:3 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign removed
Owner: set to ryandesign
Port: GraphicsMagick added; octave removed
Status: newaccepted
Summary: octave: binary not compatible with new GraphicsMagick versionGraphicsMagick @1.3.32: gm identify crashes

Thanks. I think this is GraphicsMagick bug https://sourceforge.net/p/graphicsmagick/bugs/609/. I can reproduce the problem just using gm identify, not using octave. Let me test a fix for that.

comment:4 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: acceptedclosed

In 2fe07c791cf3df873ab41f6cd57a40cbe3f5e7a9/macports-ports (master):

GraphicsMagick: Fix crash with png files

Closes: #58693

Note: See TracTickets for help on using tickets.