Re: [Wxlua-users] Thinger. A DX7 editor for SysEx data transfer to DX7, FS1R etc.

[The D. <the...@bl...>]

I've just seen my first wxLua crash.

WXLUA caused a stack fault in module WXMSW254_VC_WXLUA.DLL at 016f:100d10eb.
Registers:
EAX=1058adb8 CS=016f EIP=100d10eb EFLGS=00010216
EBX=008afa06 SS=0177 ESP=007b1fd4 EBP=007b2000
ECX=ffffffff DS=0177 ESI=00008a2a FS=18bf
EDX=00000000 ES=0177 EDI=008af9bc GS=0000
Bytes at CS:EIP:
89 4d f8 8b 55 08 8b 42 04 89 45 fc 83 7d f8 ff 
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 007b202c 100d072a 1058adb8 00efa400 007b2074

It happens consistently, as a result of using X:SetEventHandler(PANEL), where X is a button or other control whose event handling is set elsewhere for common handling of mouse clicks. The program is running ok as far as I know, until the crash is invoked by changing the OS colour scheme. (I discovered this while changing it to see the effects of using wx.wxNullColour.) I commented out all the new code to eliminate things until the bug didn't happen, then looked at what addition would alone be enough to cause the crash when the OS scheme was changed, and it's definitely that X:SetEventHandler(PANEL) bit. Even with NO code affecting colours by explicit demand, this happens.