Re: [lmi] [PATCH] Add undisplayable_exception

[Greg Chicares]

On 2014-10-09 00:41Z, Vadim Zeitlin wrote:
> On Wed, 08 Oct 2014 15:33:35 +0000 Greg Chicares <address@hidden> wrote:
[...]
> GC> Perhaps the SendMessage(WM_MDISETMENU) failure for insufficient
> GC> storage is merely incidental and uninteresting.

FWIW, I'm still seeing that diagnostic...more below.

>  Strangely enough, I don't see it here:
> 
>       % gdb --args ./lmi_wx_shared.exe --data_path=/opt/lmi/data --xxx_yyyy
>       Reading symbols from ./lmi_wx_shared.exe...done.
>       (gdb) r
>       Starting program: /opt/lmi/bin/lmi_wx_shared.exe 
> --data_path=/opt/lmi/data --xxx_yyyy
>       [New Thread 848.0x52c]
>       Program received signal SIGSEGV, Segmentation fault.
>       0xfeeefeee in ?? ()
> 
> i.e. it just crashes outright, without any warnings. Also, looking slightly
> ahead, it doesn't give this message even when using wxWidgets 3.1 (current
> trunk), where it doesn't crash (but the MDI code didn't change in 3.1). I
> think it might be due to using a different OS, as I'm testing this under
> Windows 7, while you are presumably using Windows XP.

I'm still seeing it with wx-3.1, running under 32-bit msw-xp-sp3:
  In file ../src/msw/mdi.cpp at line 1453:
  'SendMessage(WM_MDISETMENU)' failed with error 0x00000008
  (not enough storage is available to process this command.).
so I guess it must be an OS difference.

Not wanting to dismiss it too cavalierly, I tried moving the call to
InitMenuBar() a bit later, to follow this:
        frame_->Show(true);
        SetTopWindow(frame_);
but the same message still appears.

I cannot observe any incorrect behavior: the menu seems perfectly correct.
The "not enough storage" message sounds scary, but "task manager" shows
no attempt to grab appreciable RAM, and I have 2 GB free. Should we just
write this off as some goofy msw defect?