| 1 |
Debugging imagemagick can be difficult, so you can help by following |
| 2 |
these guidelines. |
| 3 |
|
| 4 |
First you should verify that the problem is in imagemagick and not the |
| 5 |
graphicksmagick compatibility package. Run "convert -version" in a |
| 6 |
terminal; if you see "GraphicsMagick" in the first line of output, please |
| 7 |
make your report against the graphicsmagick package. |
| 8 |
|
| 9 |
Otherwise, please provide a test-case that can reproduce the bug: |
| 10 |
|
| 11 |
1. Install debugging packages. |
| 12 |
2. Repeat the command line that led to the bug. To ensure you are using |
| 13 |
the imagemagick versions, replace convert, display, identify, or |
| 14 |
mogrify with convert-im7.q16, display-im7.q16, identify-im7.q16, |
| 15 |
or mogrify-im7.q16 in your test-case. |
| 16 |
|
| 17 |
3. If imagemagick dumps core, please attach a backtrace - see |
| 18 |
"http://wiki.debian.org/HowToGetABacktrace". |
| 19 |
|
| 20 |
Document the exact command line used, and attach the input files to your |
| 21 |
bug report. If the input files are in SVG format, please also run the |
| 22 |
commands |
| 23 |
"rsvg-convert yourinput.svg > rsvg.png" (from the package librsvg2-bin) |
| 24 |
and "inkscape yourinput.svg --export-png=inkscape.png" (from the package |
| 25 |
inkscape). Include the PNG output files in your bug report. |
| 26 |
|