Page 1 of 1

convert segmentation fault

Posted: 2009-12-05T19:46:23-07:00
by kentfrazier
convert -version
Version: ImageMagick 6.5.8-3 2009-12-05 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2009 ImageMagick Studio LLC
Features: OpenMP

frazier@POGO-LINUX:~$ gdb convert
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/bin/convert...done.
(gdb) run ./view0013.dcm v.jpg
Starting program: /usr/local/bin/convert ./view0013.dcm v.jpg
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
ReadDCMImage (image_info=0x805a638, exception=0x80511d8) at coders/dcm.c:3437
3437 stream_info->offsets=(ssize_t) ReadBlobLSBLong(image);
(gdb)

~$ ls -l view0013.dcm
-rwxrwxrwx 1 frazier frazier 188360 1932-02-13 22:41 view0013.dcm

~$ uname -a
Linux POGO-LINUX 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Re: convert segmentation fault

Posted: 2009-12-06T07:53:26-07:00
by magick
Post a URL to your image so we can download it and reproduce the problem. ImageMagick passes our DICOM regression tests which includes upwards of 100 different types of DICOM images.

Re: convert segmentation fault

Posted: 2009-12-06T12:05:32-07:00
by kentfrazier
http://kfrazier.mooo.com/html/imagemagick/view0013.dcm

is an example of a dcm file that causes the segmentation error.

Re: convert segmentation fault

Posted: 2009-12-06T12:16:50-07:00
by magick
We can reproduce the problem you posted and will have a patch in the next point release of ImageMagick. Thanks.

Re: convert segmentation fault

Posted: 2009-12-06T13:02:27-07:00
by kentfrazier
Thanks... looks like the problem may be that this is a SIEMANS proprietary SPI format