This is kind of a combined wxwidgets/wxpython question…
My app has been crashing with the following stack trace (OSX, but I don’t think this is OSX specific):
0 libwx_macu-2.8.0.dylib 0x013b5e4d wxWindowBase::ReleaseMouse() + 61
1 core.so 0x01044266 _wrap_Window_ReleaseMouse + 86 (_core_wrap.cpp:39363)
2 org.python.python 0x000c1d6e PyEval_EvalFrameEx + 19502
3 org.python.python 0x000c3e9d PyEval_EvalCodeEx + 2109
4…rest of stack trace clipped
So, I looked at the source code in wxwidgets for
wxWindowBase::ReleaseMouse() (2.8.11.0), and added this assert at the top, which is present in the 2.9.1 tree of wxwidgets, hoping it would fix the problem. Specifically, I put this in src/common/wincmn.cpp, at the top of ReleaseMouse:
// DGH ADD FROM 2.9.1.1
wxASSERT_MSG( ms_winCaptureCurrent == this, “attempt to release mouse, but this window hasn’t captured it” );
I also placed if checks around all pointer usages in that routine, but I don’t think any of them are getting triggered, but I can’t say for sure. App still crashes, but with a slightly different stack trace. It looks like it got past the ReleaseMouse routine, but now dies in the swig wrapper.
0 org.python.python 0x00041c9a int__format__ + 266
1 core.so 0x01044266 _wrap_Window_ReleaseMouse + 86 (_core_wrap.cpp:39363)
2 org.python.python 0x000c1d6e PyEval_EvalFrameEx + 19502
3 org.python.python 0x000c3e9d PyEval_EvalCodeEx + 2109
4…rest of stack trace clipped.
I don’t see a int__format__ function or anything inside
_wrap_Window_ReleaseMouse…so do these little tidbits of information mean anything to anyone? I’m stuck, and hoping that some little glimmer of information might lead to me figuring this out.