I have successfully built the fife engine from latest SVN. I've also tried the FIFE_2008.0_r2109_src release with the same results. I'm using glibc 2.6.1, and I'm on Ubuntu 7.10.
This is the last part of my stack trace:
==23599== by 0x4A146B8: FIFE::Pool::get(unsigned, bool) (pool.cpp:103)
==23599== by 0x49BC3EE: FIFE::ImagePool::getImage(unsigned) (imagepool.h:54)
==23599== by 0x4ABDB15: _wrap_ImagePool_getImage (fife_wrap.cxx:84751)
==23599== by 0x805C786: PyObject_Call (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C6C2E: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C9CA4: PyEval_EvalCodeEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8168: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8EA4: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8EA4: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== Address 0x4 is not stack'd, malloc'd or (recently) free'd
==23599==
==23599== Process terminating with default action of signal 11 (SIGSEGV)
==23599== Access not within mapped region at address 0x4
==23599== at 0x5282096: __cxa_allocate_exception (in /usr/lib/libstdc++.so.6.0.9)
==23599== by 0x49E6D92: FIFE::SubImageLoader::loadResource(FIFE::ResourceLocation const&) (subimage_loader.cpp:49)
==23599== by 0x4A13E7A: FIFE::Pool::findAndSetProvider(FIFE::Pool::PoolEntry&) (pool.cpp:204)
==23599== by 0x4A146B8: FIFE::Pool::get(unsigned, bool) (pool.cpp:103)
==23599== by 0x49BC3EE: FIFE::ImagePool::getImage(unsigned) (imagepool.h:54)
==23599== by 0x4ABDB15: _wrap_ImagePool_getImage (fife_wrap.cxx:84751)
==23599== by 0x805C786: PyObject_Call (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C6C2E: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C9CA4: PyEval_EvalCodeEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8168: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8EA4: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599== by 0x80C8EA4: PyEval_EvalFrameEx (in /home/daniel/devel/virtualenv/bin/python)
==23599==
Does this ring a bell? Am I using an incompatible version of some library? Anything else that I could check?