[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi] Segfault in lmi with wx-2.9.5
From: |
Greg Chicares |
Subject: |
[lmi] Segfault in lmi with wx-2.9.5 |
Date: |
Fri, 12 Jul 2013 19:36:09 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 |
A segfault occurred while I was randomly pounding on a fresh
lmi build. I haven't been able to reproduce it yet. The DrMingw
JIT debugger caught it and issued the report below; can you
make any sense of it?
Usually DrMingw gives a backtrace; here it did not.
80000003 seems to be a breakpoint, but I don't remember coding
INT 3 anywhere. That would be opcode 0xCC; perhaps execution
jumped into a data area that happened to contain that opcode?
The ensuing C0000005 is of course a segfault. Using 'addr2line',
I can't decode the address for either "ExceptionCode", or for
the other "AddrPC" in the call stack:
addr2line --exe=./lmi_wx_shared.exe 03DAD2AA
addr2line --exe=./lmi_wx_shared.exe 7C90120E
addr2line --exe=./lmi_wx_shared.exe 2E00225A
all return "??:0", even though lmi was built with '-ggdb'.
Is there anything else I can do with this debug report?
DEBUG_EVENT:
dwDebugEventCode = EXCEPTION_DEBUG_EVENT
dwProcessId = 274
dwThreadId = 1D4C
ExceptionCode = 80000003
ExceptionFlags = 0
ExceptionAddress = 7C90120E
dwFirstChance = 1
DEBUG_EVENT:
dwDebugEventCode = EXCEPTION_DEBUG_EVENT
dwProcessId = 274
dwThreadId = F10
ExceptionCode = C0000005
ExceptionFlags = 0
ExceptionAddress = 3DAD2AA
dwFirstChance = 0
lmi_wx_shared.exe caused an Access Violation at location 03dad2aa Writing to
location 0021323f.
Registers:
eax=b40386d2 ebx=03c4c00b ecx=0022ef26 edx=03dad260 esi=d2f803ca edi=03c44b10
eip=03dad2aa esp=0021c64a ebp=00225a51 iopl=0 nv up ei ng nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286
Call stack:
AddrPC AddrReturn AddrFrame AddrStack Params
03DAD2AA 2E00225A 00225A51 0021C64A 186E748D DC0059BD 7400225C
E900225A
03DAD2AA
2E00225A 00000000 0022EE5C 0021C64A 6F483DA3 03C4C008 FFFFFFFF
0022EEC0
2E00225A
DEBUG_EVENT:
dwDebugEventCode = EXIT_THREAD_DEBUG_EVENT
dwProcessId = 274
dwThreadId = 1D4C
dwExitCode = 0
DEBUG_EVENT:
dwDebugEventCode = EXIT_PROCESS_DEBUG_EVENT
dwProcessId = 274
dwThreadId = F10
dwExitCode = C0000005
- [lmi] Segfault in lmi with wx-2.9.5,
Greg Chicares <=
- Re: [lmi] Segfault in lmi with wx-2.9.5, Vadim Zeitlin, 2013/07/12
- Re: [lmi] Segfault in lmi with wx-2.9.5, Greg Chicares, 2013/07/13
- Re: [lmi] Segfault in lmi with wx-2.9.5, Vadim Zeitlin, 2013/07/13
- Re: [lmi] Segfault in lmi with wx-2.9.5, Greg Chicares, 2013/07/14
- Re: [lmi] Segfault in lmi with wx-2.9.5, Vadim Zeitlin, 2013/07/14
- Re: [lmi] Segfault in lmi with wx-2.9.5, Vadim Zeitlin, 2013/07/14
- Re: [lmi] Segfault in lmi with wx-2.9.5, Greg Chicares, 2013/07/19
- Re: [lmi] Segfault in lmi with wx-2.9.5, Vadim Zeitlin, 2013/07/19