On Sun, 8 Aug 2010, Christopher Martin wrote:
I suspect that the crash is related to this problem:
https://www-old.cae.wisc.edu/pipermail/octave-maintainers/2010-January/014891.html
Thus it may be a xine-lib bug after all, as I don't see any
InitializeMagick() - or DestroyMagick() for that matter - calls in
xine-lib's code. I would guess that libxinevdec/image.c would be the
appropriate place to add them.
The next release of GraphicsMagick will make
InitializeMagick()/DestroyMagick() totally thread safe. In general it
is safe to invoke InitializeMagick() just prior to use (and any number
of times) so that life is easier within a library context. The
overhead of invoking InitializeMagick() is quite low since if the
library is already initialized, the function immediately returns.
I am considering using GCC's shared library contructor/destructor
semantics but am not sure how reliable that might be.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
