Legacy ImageMagick Discussions Archive

Unfortunately we cannot reproduce the problem. We get expected results with ImageMagick 6.9.6-4 under CentOS 7 compiled with the gcc address sanitizer enabled
Khmm... I doubt, this is OS-specific, but it may be compiler-specific -- FreeBSD uses clang by default ("cc" means clang-3.4.1 here ...

I tried to identify an image, while it was still being saved by scanimage. Instead of either successfully identifying or outputting an error-message, the utility crashed. Using ImageMagick 6.9.6-4 Q16 amd64 2017-03-15 on FreeBSD. According to gdb, the stack is:

Core was generated by `identify ...

Is this also the cause of the problem reported here: viewtopic.php?f=3&t=26745? No. As I write in that thread, that problem can be seen -- by running under valgrdin --- even on a different CPU-architecture (amd64).
ImageMagick utilizes a configure script generated by the automake / autoconf ...

The CFLAGS I'm specifying to configure script are:

-O2 -pipe -march=core2 -I/opt/include/graphviz -I/opt/include/freetype2 -fstack-protector -fno-strict-aliasing

For some reason, after configure finishes, it reports:
CFLAGS = -I/opt/include/lqr-1 -I/opt/include/glib-2.0 -I/opt/lib/glib-2.0 ...

What version of IM are you using?
As per subject, I'm seeing this problem with 6.9.0-0.
Does this happen on all input images, or just this one? If just this one, please supply the input file.
Seems to happen before the image is even accessed -- for example, with a bogus (nonexistent) filename ...

Trying to convert an image, I got convert to suddenly crash. Rerunning the same command-line under valgrind, I see the following errors (before the actual crash even happens):

==15439== Command: convert -bordercolor Transparent -border 1x1 ../Tango/22x22/actions/document-print-preview.png 24x24 ...

There are two patch-files in FreeBSD's port graphics/libfpx, that fix various warnings raised by newer compilers (clang-3.2, gcc-4.8). The patches are applicable to 1.3.1-2:

• Remove unused private fields from some classes
• Fix a variety of warnings and a few errors

The ReadPage() and ReadPageLine() methods must've been returning int at some point so the calling method tried to analyze the response to turn it into a probable FPXStatus (an enum).

The methods now (and since, at least, 1.2) are already returning FPXStatus themselves, so the analysis is not ...

The same virtual method (CreateEmptyResolutionLevel) is declared with a slightly different signature in the two files.

GNU C++ did not mind, but clang is throwing a warning. The below patch (already part of FreeBSD port graphics/libfpx ) resolves the problem by using the signature of the ...

The original patch is from Andriy Gapon. It is now part of the FreeBSD port graphics/libfpx .
--- fpx/f_fpxvw.cpp 2005-02-25 21:23:05.000000000 -0500
+++ fpx/f_fpxvw.cpp 2012-01-19 19:44:34.425688599 +0200
@@ -613,6 +613,7 @@ HRESULT OleRegGetUserType(REFCLSID clsid
const OLECHAR *src=OLESTR ...

Hello!

Amazon's Kindle can show pictures. However, storing the full-color ones on it is wasteful, because it only has a black-and-white screen.

What options should I give to convert to get "optimal" JPGs or PNGs: 600x800, with 16 shades of gray -- and otherwise follow these recommendations ...

Then the new release should've been made into 6.4.0-12 -- and no other unrelated changes should've found its way into it.

In addition to the bug-fix you describe (with -fx), between the "bad" and the "good" instances of 6.4.0-11 not only did vast changes to Makefiles and ChangeLog take place, but ...

Could this new one be renamed into 6.4.0-12 and the previous 6.4.0-11 reinstated? Thanks!

Hello!

I upgraded FreeBSD port of ImageMagick to 6.4.0-11 recently, but this morning a user notified me, that the distribution file on your FTP-site no longer matches the size and the checksums I worked with.

Indeed, the file appears to have been rerolled and the differences are non-trivial.

In ...

Hello!

A user has alerted me recently, that building the FreeBSD port of IM, which I just updated to 6.4.0-7, warns that options --without-dot and --without-mpeg2 are unrecognized.

What is the right way of disabling these, when one wants to build IM on a machine, for the corresponding packages may ...