Lion Compatibility?

[flying toaster]

As far as I'm concern CivIV works fine under Snow Leopard but it is another thing under Lion.
The installation wasn't easy and got some problems along the way and have crashes from time to time. And no matter if I play with a mod or not ( from the game or not )

Enclosed is the crash I mostly get, it crashes when the map is suppose to appear at the beginning of a game ...
And I'm not talking about some python calling, when I remove PythoncallbackDefines.xml my hard drive dissapear from the Desk ...

Spoiler :

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Toy Files/*/Civilization IV Beyond the Sword.app/Contents/MacOS/Civilization IV Beyond the Sword
__TEXT 0000000000001000-0000000001340000 [ 19.2M] r-x/rwx SM=COW /Applications/Toy Files/*/Civilization IV Beyond the Sword.app/Contents/MacOS/Civilization IV Beyond the Sword

Application Specific Information:
objc[2126]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_c.dylib 0x97073d50 strlen + 16
1 org.python.python 0x024e6b9e PyString_FromString + 36
2 com.aspyr.civ4bts 0x0038ee17 boost:ython::detail::caller_arity<2u>::impl<char const* (CyGlobalContext::*)(int) const, boost:ython::default_call_policies, boost::mpl::vector3<char const*, CyGlobalContext&, int> >:perator()(_object*, _object*) + 127
3 com.aspyr.civ4bts 0x005b129e boost:ython:bjects::function::call(_object*, _object*) const + 698
4 com.aspyr.civ4bts 0x005b3071 boost::detail::function::void_function_obj_invoker0<boost:ython:bjects:anonymous namespace)::bind_return, void>::invoke(boost::detail::function::any_pointer) + 35
5 com.aspyr.civ4bts 0x005ace0f boost::function0<void, std::allocator<boost::function_base> >:perator()() const + 79
6 com.aspyr.civ4bts 0x005acab6 boost:ython::handle_exception_impl(boost::function0<void, std::allocator<boost::function_base> >) + 54
7 com.aspyr.civ4bts 0x005b1ebf bool boost:ython::handle_exception<boost:ython:bjects:anonymous namespace)::bind_return>(boost:ython:bjects:anonymous namespace)::bind_return) + 41
8 com.aspyr.civ4bts 0x005b018c function_call + 58
9 org.python.python 0x024bcf2d PyObject_Call + 46
10 org.python.python 0x0250c847 0x24b6000 + 354375
11 org.python.python 0x0250e2b9 0x24b6000 + 361145
12 org.python.python 0x0250c7e3 0x24b6000 + 354275
13 org.python.python 0x0250e2b9 0x24b6000 + 361145
14 org.python.python 0x0250c7e3 0x24b6000 + 354275
15 org.python.python 0x0250e150 PyEval_EvalCodeEx + 1960
16 org.python.python 0x024cf8de 0x24b6000 + 104670
17 org.python.python 0x024bcf2d PyObject_Call + 46
18 org.python.python 0x0250899c PyEval_CallObjectWithKeywords + 220
19 org.python.python 0x024bd82c PyObject_CallObject + 32
20 com.aspyr.civ4bts 0x00678e6f FPythonMgr::ICallFunction(_object*, std::string const&, _object*, _object**) const + 79
21 com.aspyr.civ4bts 0x006790e7 FPythonMgr::ICallFunction(_object*, std::string const&, _object*, long*) const + 57
22 com.aspyr.civ4bts 0x00679744 FPythonMgr::CallFunction(std::string const&, std::string const&, _object*, long*) const + 180
23 com.aspyr.civ4bts 0x00b1d598 CyPythonMgr::callFunction(FStringA const&, FStringA const&, void*, long*) + 178
24 com.aspyr.civ4bts 0x00c10d8a CvWorldBuilder::saveDesc(char const*) + 326
25 com.aspyr.civ4bts 0x00c10ef9 CvWorldBuilder::quickSave() + 73
26 com.aspyr.civ4bts 0x00a91555 CvApp::InitGame() + 3891
27 com.aspyr.civ4bts 0x00a8bbbb CvApp::Init(HINSTANCE__*, char const*) + 2285
28 com.aspyr.civ4bts 0x00b1ee41 WinMain + 33
29 com.aspyr.civ4bts 0x000a7f99 sEventLoopEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 111
30 com.apple.HIToolbox 0x951a2dec _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
31 com.apple.HIToolbox 0x9501e4f3 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1602
32 com.apple.HIToolbox 0x9501d970 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 482
33 com.apple.HIToolbox 0x9501d788 SendEventToEventTargetWithOptions + 75
34 com.apple.HIToolbox 0x950333aa _ZL29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv + 3152
35 com.apple.HIToolbox 0x9501e9ae _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 2813
36 com.apple.HIToolbox 0x9501d970 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 482
37 com.apple.HIToolbox 0x95032755 SendEventToEventTarget + 76
38 com.apple.HIToolbox 0x951a2c38 ToolboxEventDispatcher + 82
39 com.apple.HIToolbox 0x951a2d67 RunApplicationEventLoop + 236
40 com.aspyr.civ4bts 0x000a8052 InstallEventsAndRunGameLoop() + 166
41 com.aspyr.civ4bts 0x000a83ea main + 356
42 com.aspyr.civ4bts 0x00002642 _start + 216
43 com.aspyr.civ4bts 0x00002569 start + 41

 

[AlanH]

It's crashing in Python code. I don't understand your point about removing the PythonCallbackDefines.xml file. Removing one file from your installation is likely to create new and different problems, and is unlikely to fix anything.

To find out where Python is failing, I suggest you enable Logging in the config.ini file and relaunch the game. When the crash happens, look at the Logs/PythonDbg.log file. Post it here if you don't understand what it is telling you.