Mark Duling wrote:

Joerg van den Hoff <j.van_den_hoff@fz-rossendorf.de> on Tuesday, October 24, 2006 at 5:52 AM -0800 wrote:

...

hi everybody,

attempting to use `montage' from teh imageMagick package with something like

leads to a crash with the error message

magick/cache.c:2385: failed assertion `cache_info->number_views != 0UL'

this is with version ImageMagick 6.2.7 08/29/06 installed in the 'old' darwinports times, but this seems to be the current version, still.

I tried the same with the most recent version provided via fink (6.1.8 08/28/06): there, everything runs smoothly.

any ideas appreciated.

6.2.9-8 is current for ImageMagick. Sounds like you haven't done a 'port selfupdate' in awhile. See if the new version fixes it.

Mark

thanks a lot. fact is, port `montage -version' yielded 6.2.7 _and_ `port outdated' did _not_ list imagemagick so I thought everything was fine (`port selfupdate' told me that everything was up to date). but nevertheless `port info imagemagick' reported 6.2.9.8 as current version, no idea why `port' did not list imagemagick as outdated. anyway, I now uninstalled/cleaned imagemagick and reinstalled, so now 6.2.9.8 is running. but the problem with montage persists, only slightly different: montage -tile 2x2 i1.png i2.png i3.png i4.png now simply gives a Bus error. the tail of the `ktrace' output reads ... 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "/opt/local/share/ImageMagick-6.2.9/type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "/Users/vdh/.magick/type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage PSIG SIGBUS SIG_DFL which to me only shows that some file `type.xml' is nowhere found but seems to be needed to procede ... any more hints? regards, joerg

On Oct 25, 2006, at 03:49, Joerg van den Hoff wrote:

...

6.2.9-8 is current for ImageMagick. Sounds like you haven't done a 'port selfupdate' in awhile. See if the new version fixes it.

thanks a lot. fact is, port `montage -version' yielded 6.2.7 _and_ `port outdated' did _not_ list imagemagick so I thought everything was fine (`port selfupdate' told me that everything was up to date). but nevertheless `port info imagemagick' reported 6.2.9.8 as current version, no idea why `port' did not list imagemagick as outdated.

Well, understand what each command does: "port outdated" checks if any installed ports are outdated, compared with the portindex that's currently on your machine. When you ran "port outdated", your portindex was apparently still rather old, so it told you nothing was outdated. "port sync" downloads the current portindex. "port selfupdate" is a combination of two things: "port sync" and also upgrading the base MacPorts software, if necessary. The message you got told you that the base MacPorts software did not need updating. This has nothing to do with your installed ports, however. After running "port selfupdate", you now have the current portindex. If at this point you had again run "port outdated" you would have seen that ImageMagick was outdated. So the correct way to periodically see if you need to update anything is to run "sudo port sync" followed by "port outdated". And if you see an announcement on the list that a new version of MacPorts is available, then you should run "sudo port selfupdate". Or you could schedule a selfupdate to occur regularly, for example every month, using cron.

Emmanuel Hainry wrote:

Citando Joerg van den Hoff :

...

Mark Duling wrote:

...

Joerg van den Hoff <j.van_den_hoff@fz-rossendorf.de> on Tuesday, October 24, 2006 at 5:52 AM -0800 wrote:

...

hi everybody,

attempting to use `montage' from teh imageMagick package with something like

leads to a crash with the error message

magick/cache.c:2385: failed assertion `cache_info->number_views != 0UL'

this is with version ImageMagick 6.2.7 08/29/06 installed in the 'old' darwinports times, but this seems to be the current version, still.

I tried the same with the most recent version provided via fink (6.1.8 08/28/06): there, everything runs smoothly.

[...] anyway, I now uninstalled/cleaned imagemagick and reinstalled, so now 6.2.9.8 is running.

but the problem with montage persists, only slightly different:

montage -tile 2x2 i1.png i2.png i3.png i4.png

now simply gives a Bus error. the tail of the `ktrace' output reads

... 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "/opt/local/share/ImageMagick-6.2.9/type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "/Users/vdh/.magick/type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage CALL open(0xbfff7778,0,0x30fde0) 8300 montage NAMI "type.xml" 8300 montage RET open -1 errno 2 No such file or directory 8300 montage PSIG SIGBUS SIG_DFL

which to me only shows that some file `type.xml' is nowhere found but seems to be needed to procede ...

It is found, exactly where it has been installed (and in the first place montage searches): "/opt/local/lib/ImageMagick-6.2.9/config/type.xml". Moreover, if I put this file in '.', the lines before SIGBUS signal a success. So the bus error is not due to this file.

...

any more hints?

Unfortunately, no

right, I find the succssful open in the ktrace.out file, too further upstream in the file (sorry for stating the opposite in the first place). but I understand you get the same Bus Error? I'm not sure what to do now: is this considered a macports problem or a genuine imagemagick bug. where should this be reported?

On Oct 26, 2006, at 02:51, Joerg van den Hoff wrote:

...

the command given above (montage -tile 2x2 i1.png i2.png i3.png i4.png) completes successfully for me with the same ImageMagick version. I didn't see what architecture you're on; I'm on PowerPC. so I am (dual G5, 10.4.8)

I'm on a PowerBook G4 with 10.4.8. Maybe it's a G5 or a dual- processor thing.

...

Note that the command tiles the images i1.png, i2.png and i3.png, and writes the result to i4.png. right (I missed adding the output file), but apending `out.png' to the command leads to the same crash anyway. Perhaps the crash has to do with the specific images you're using. If you want to send me the images (off-list if you like) I'll see if I can reproduce the crash then. I tried it with several sets of different images (jpg and png) - same result. furthermore I tried the imagemagick version provided by `fink' (ImageMagick 6.1.8): this one runs flawless. so thanks very much for the offer to try out this specific images, but I think the reason is not in the images. maybe something is wrong with my /opt/local tree but I don't see what it could be.

I was going to suggest reinstalling ImageMagick, then remembered that you just upgraded to 6.2.9-8 so that should be ok. You could report it to the ImageMagick bugs mailing list and see what they say. http://www.archivesat.com/list685.htm You may want to wait and test 6.3.0-0 first. I just committed that update, so if you wait 12 hours, then "sudo port sync", you should be able to upgrade.