[Pyobjc-dev] Getting a better stack trace with PyObjc possible?

[Marc V. O. <mar...@gm...>]

hi,

I looked around the web and more specific stack overflow: I was hoping if
there is something I can do to have a better stack trace from pyobjc/python.

For example my end users send me this, after a hard crash.

0 libobjc.A.dylib 0x99b51c22 (anonymous
namespace)::AutoreleasePoolPage::pop(void*) + 350
1 com.apple.CoreFoundation 0x97b2c515 _CFAutoreleasePoolPop + 53
2 com.apple.Foundation 0x96316b87 -[NSAutoreleasePool release] + 131
3 com.apple.CoreFoundation 0x97b01749 CFRelease + 169
4 _objc.so 0x04019c21 object_dealloc + 257
5 org.python.python 0x01c6e2cf subtype_dealloc + 575
6 org.python.python 0x01c3a041 frame_dealloc + 385
7 org.python.python 0x01ced87c tb_dealloc + 156
8 org.python.python 0x01ced88c tb_dealloc + 172
9 org.python.python 0x01c52179 PyDict_DelItem + 249
10 org.python.python 0x01c52251 PyDict_DelItemString + 49
11 org.python.python 0x01cb940a PyEval_EvalFrameEx + 4810
12 org.python.python 0x01cbd6a6 PyEval_EvalFrameEx + 21862
13 org.python.python 0x01cbd6a6 PyEval_EvalFrameEx + 21862
14 org.python.python 0x01cbd6a6 PyEval_EvalFrameEx + 21862
15 org.python.python 0x01cbd6a6 PyEval_EvalFrameEx + 21862
16 org.python.python 0x01cbee9d PyEval_EvalCodeEx + 2109
17 org.python.python 0x01c3ba36 function_call + 166
18 org.python.python 0x01c0a315 PyObject_Call + 85
19 org.python.python 0x01c1c8e6 instancemethod_call + 422
20 org.python.python 0x01c0a315 PyObject_Call + 85
21 org.python.python 0x01cb717e PyEval_CallObjectWithKeywords + 78
22 org.python.python 0x01cf89d6 t_bootstrap + 70
23 libsystem_c.dylib 0x957c2ed9 _pthread_start + 335
24 libsystem_c.dylib 0x957c66de thread_start + 34


Would be nice to know which method and object was called at

PyEval_EvalFrameEx + 21862

for example.

Marc