The GraphicsMagick 1.3.17 release fixes the SVG crasher bug.
However, there is a small rendering flaw which causes the output to
not be good enough for rendering the ImageMagick logo. I don't know
the cause of this rendering flaw. ImageMagick does not seem to cause
it if it is used to render
On Tue, Aug 28, 2012 at 6:18 PM, Bob Friesenhahn
wrote:
> On Tue, 28 Aug 2012, Bastien ROUCARIES wrote:
>
>> On Tue, Aug 28, 2012 at 5:55 PM, Bob Friesenhahn
>> wrote:
>>>
>>> I was confused. I see that the problem report is actually with reading
>>> XPM
>>> rather than SVG. I tried reading the
On Tue, 28 Aug 2012, Bastien ROUCARIES wrote:
On Tue, Aug 28, 2012 at 5:55 PM, Bob Friesenhahn
wrote:
I was confused. I see that the problem report is actually with reading XPM
rather than SVG. I tried reading the XPM on a Solaris 10 SPARC system and
it did not cause GM to crash. Testing wi
On Tue, Aug 28, 2012 at 5:55 PM, Bob Friesenhahn
wrote:
> I was confused. I see that the problem report is actually with reading XPM
> rather than SVG. I tried reading the XPM on a Solaris 10 SPARC system and
> it did not cause GM to crash. Testing with a more stringent memory
> allocator is re
This issue may be related to GraphicsMagick bug ID 3411492, which is
not yet fixed
(https://sourceforge.net/tracker/?func=detail&aid=3411492&group_id=73485&atid=537937).
The code seems to access beyond the current DrawInfo stack.
I would appreciate it if someone can point me to where I can eas
Package: graphicsmagick
Version: 1.3.16-1
Severity: serious
Dear graphickmagick team,
graphicksmagick segfault on sparc during build of imagemagick
/usr/bin/convert
/build/buildd-imagemagick_6.7.7.10-4-sparc-7q9mNX/imagemagick-6.7.7.10/debian/display.im6.svg
-resize 32x32 \
/buil
6 matches
Mail list logo
