Re: [lmi] Segfault in lmi with wx-2.9.5

[Greg Chicares]

On 2013-07-12 21:31Z, Vadim Zeitlin wrote:
> On Fri, 12 Jul 2013 19:36:09 +0000 Greg Chicares <address@hidden> wrote:
[...]
> GC> The ensuing C0000005 is of course a segfault. Using 'addr2line',
> GC> I can't decode the address for either "ExceptionCode", or for
> GC> the other "AddrPC" in the call stack:
> GC>   addr2line --exe=./lmi_wx_shared.exe 03DAD2AA
> GC>   addr2line --exe=./lmi_wx_shared.exe 7C90120E
> GC>   addr2line --exe=./lmi_wx_shared.exe 2E00225A
> GC> all return "??:0", even though lmi was built with '-ggdb'.
> GC> Is there anything else I can do with this debug report?
> 
>  Unfortunately I don't know, debugging with MinGW under Windows is really
> difficult, at least compared to Microsoft tools... Perhaps you could load
> it into gdb and use "disassemble *0x3DAD2AA" in it?

Thanks for the idea. Even that doesn't work, though:

/opt/lmi/bin[0]$gdb lmi_wx_shared.exe
GNU gdb (GDB) 7.6.50.20130508-cvs (cygwin-special)
[...]
Reading symbols from /opt/lmi/bin/lmi_wx_shared.exe...done.
(gdb) disassemble *0x3DAD2AA
Cannot access memory at address 0x3dad2aa

And the '.map' file doesn't seem to help, either.

I guess all I can do is try somehow to reproduce it.

Would it be feasible to log all events, so that once a
random segfault is observed, a log could be played back
with a fair possibility of reproducing the problem?

Should the planned GUI-testing automation have a "random"
mode that simulates a thousand monkeys entering arbitrary
(logged) input to find latent problems like segfaults?