Re: [lmi] Segfault with updated wx

[Vadim Zeitlin]

On Tue, 21 Jun 2016 14:51:58 +0000 Greg Chicares <address@hidden> wrote:

GC> We're trying to create a reproducible test case, but I thought
GC> it would be better to share this JIT debugger output right away.

 Which wx commit exactly are you using for this build? I'd have to use
exactly the same one to understand what do the addresses below correspond
to.

GC> lmi_wx_shared.exe caused an Access Violation at location 62ca834c in module 
wxmsw311u_gcc_gcc-491-97e6a75d1a83e5597942741f8382c3d4.dll Reading from 
location 00000000.
GC> 
GC> Registers:
GC> eax=047c2728 ebx=0621f310 ecx=00000000 edx=00000000 esi=047c2728 
edi=00000000
GC> eip=62ca834c esp=0022f5e0 ebp=0022f648 iopl=0         nv up ei pl nz na po 
nc
GC> cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             
efl=00000206
GC> 
GC> Call stack:
GC> AddrPC     AddrReturn AddrFrame  AddrStack  Params
GC> 62CA834C   62CA98D8   0022F648   0022F5E0   00000000   00000000   047C2728  
 62CAF03E
GC> 62CA834C  
wxmsw311u_gcc_gcc-491-97e6a75d1a83e5597942741f8382c3d4.dll:62CA834CC:\opt\lmi\local\lib\wxmsw311u_gcc_gcc-491-97e6a75d1a83e5597942741f8382c3d4.dll:
 No symbol found
GC>   _ZNK6wxGrid23GetDefaultEditorForCellEii

 So this must happen when starting to edit a cell in MultiDimGrid? AFAICS
this is the only place in lmi code where wxGrid is being used...

 Thanks,
VZ