Re: SEGV with --with-gslib for 1.1.10

On Tue, 15 Jan 2008, Albert Chin wrote:

> libgs.so and GM both use a shared libjpeg.

So there is probaly an actual bug.

>> If there is an actual bug in GraphicsMagick pertaining to use of
>> Ghostscript as a library, it would be in the
>> InvokePostscriptDelegate()  function in magick/delegate.c.
>
> I'll try to find time to debug this later. No promises though. We'll
> just build --without-gslib for now.

There are other reasons to not use Ghostscript as a library:

   1) It is not clear that use of multiple Ghostscript interpreters at
      once is thread safe.

   2) Only old versions are available as GPL, and the licensor includes
      lots of scary sounding statements in their license text.

   3) It is much more difficult for the end-user to change the version
      of Ghostscript used.

   4) Under Unix, it is not really any more efficient to use Ghostscript
      as a library since fork/exec are quite efficient.

   5) Ghostscript bugs don't become GraphicsMagick bugs.

Use of the library sounds really cool but as it turns out the library 
only provides a sort of "command line" access via an API.  If 
GraphicsMagick was to provide a Ghostscript driver (and Ghostscript 
was built to use it) then things might be different.

Bob
======================================
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/