Closed erno closed 11 years ago
I'm seeing this now after updating a laptop to 12.10 (64-bit).
I tried git bisect on this but the build was broken in most places in recent history.
due to deps changing or? mostly it has been working in history otherwise IIRC, at least we've been many using it all the time?
when i tried to bisect the recent particle system loading bug, noticed that wasn't easy as builds from different points in history didn't just work, i was thinking it was due to deps changes.
a couple of bisect points had compile errors in PythonScriptingModule and one failed in a bullet-related compile error that sounded like a deps mismatch.
I made these minimal disables to track the crash a bit, this way the module seems to run on 12.10 - didn't verify yet how much it actually works, possibly not much at all for the qt accessing, but at least doesn't crash.
https://github.com/antont/tundra/commit/a4ca32f62bf2637f405ec11e4ec3fa6a2906e400
the disabling is not minimal, possibly calling the py c api init would not make it crash.
I wonder if this has to do with how we've been using both the py c api init call and the pythonqt init mechanism.
Closing and migrating this issue to https://github.com/realXtend/TundraAddons/issues/4
Matti at Chiru ran into this after setting up a new 12.10 machine and there was earlier a mention on #realxtend-dev about it with 2 sightings reported.
Loading plugin 'PythonScriptModule'.
Program received signal SIGSEGV, Segmentation fault. 0xa7bab569 in PythonQtPrivate::createPythonQtClassWrapper(PythonQtClassInfo, char const, object) () from/rex/naali-deps/install/lib/libPythonQt.so.1
(gdb) backtrace
0 0xa7bab569 in
PythonQtPrivate::createPythonQtClassWrapper(PythonQtClassInfo, char
const, object) ()
from /rex/naali-deps/install/lib/libPythonQt.so.1
1 0xa7bace81 in PythonQtPrivate::registerCPPClass(char const, char
const, char const, QObject ()(), void ()(void,
PythonQtInstanceWrapperStruct), object, int) () from