Re: SEGV with --with-gslib for 1.1.10

On Tue, Jan 15, 2008 at 01:06:54PM -0600, Bob Friesenhahn wrote:
> On Tue, 15 Jan 2008, Albert Chin wrote:
> 
> > I've built 1.1.10 on RHEL4/x86_64 with --with-gslib against
> > Ghostscript 8.57. I'm getting a SEGV while running the testsuite:
> >  ./rwfile ./input_bilevel.miff JPEG
> >  ./rwfile ./input_gray.miff JPEG
> >  ./rwfile ./input_256c.miff JPEG
> >  ./rwfile ./input_truecolor.miff JPEG
> >
> > So, is GM doing something wrong or did we just build one of our
> > 3rd-party libs incorrectly?
> 
> Ghostscript uses libjpeg and either incorporates all of its symbols,
> or (hopefully) references it as a shared library.  GraphicsMagick
> also uses libjpeg.  If Ghostscript incorporates libjpeg into its own
> library and there is some variance between how the libjpeg that
> GraphicsMagick uses and the libjpeg that Ghostscript uses are built
> (or a difference in structure definitions), then there will surely
> be problems.  There is also a possibility of using the wrong symbols
> due to duplicate symbols in the program.  The only semi-safe
> approach is if both Ghostscript and GraphicsMagick use the same
> libjpeg as a "system" shared library and share the same libjpeg
> headers.

libgs.so and GM both use a shared libjpeg.

> 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.

-- 
albert chin ([email protected])

-------------------------------------------------------------------------
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/