Rather go to https://github.com/galfar/imaginglib/discussions
Posted by Galfar
- 18 February 2010, 23:57:53Ok thanks for more info.
I'll put a note about this problem somewhere in Imaging documentation along with a link to this thread.
I'll put a note about this problem somewhere in Imaging documentation along with a link to this thread.
Posted by kaukas
- 22 January 2010, 05:49:51Sorry 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.
Posted by Galfar
- 25 December 2009, 19:02:14Thanks 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?
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?
Posted by kaukas
- 25 December 2009, 07:21:13Because 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.
SMF spam blocked by CleanTalk