Topic: Imaging does not work when used inside shared library on freebsd (Read 571 times)

kaukas · « **on:** 25 December 2009, 07:21:13 »

Because IO functions are assigned in initialization section and there is fpc bug on freebsd (initialization/finalization are not called), Imaging crashes library. I reported bug 0015422 in fpc bug tracker about this issue. So be careful.

Galfar · « **Reply #1 on:** 25 December 2009, 19:02:14 »

Thanks for letting me know.

I'm thinking of putting the IO init code to separate procedure that could be called in ImLoadLibrary function - so IO will be inited before user calls any loading/saving functions.

Problem is ImLoadLibrary is now only used in C .so header, not in Pascal.
May I ask from which language you accessed Imaging as shared library?

kaukas · « **Reply #2 on:** 22 January 2010, 05:49:51 »

Sorry for late reply. If you still interesting, the library was loaded from postgresql for so called "c style functions" (in my case they are actually written in pascal). After workaround mentioned in fpc bug report, there is no problems and library that uses imaging works very well on freebsd production server. Postgresql is written in c, but that doesn't matter because this bug would appear in any software while loading library with dlopen on bsd systems. Bug exists for several years and I don't think it will be resolved in the near future.

Galfar · « **Reply #3 on:** 18 February 2010, 23:57:53 »

Ok thanks for more info.
I'll put a note about this problem somewhere in Imaging documentation along with a link to this thread.

News:

Author Topic: Imaging does not work when used inside shared library on freebsd (Read 571 times)

kaukas

Imaging does not work when used inside shared library on freebsd

Galfar

Re: Imaging does not work when used inside shared library on freebsd

kaukas

Re: Imaging does not work when used inside shared library on freebsd

Galfar

Re: Imaging does not work when used inside shared library on freebsd