Tue 19 Jun 2007 02:49:15 PM UTC, comment #1:
Here is evidence of an actual defect on msw.
Symptom: a messagebox is supposed to contain an extremely
long string, but it doesn't appear at all. This fails
silently after eating a few billion machine cycles.
Suspected cause: Perhaps the native ::MessageBox() call
fails and wx does not report that?
Importance: None, really, if we replace wxMessageBox()
with an alternative facility that doesn't use a native
messagebox. Until then, a horrendously-defective xsl file
could conceivably elicit this behavior, but we would strive
not to release such a thing. However, we'd like to get this
fixed, at least so that wx would display some fallback
"messagebox couldn't be displayed" diagnostic, because we
might still use wxMessageBox() in some situations.
To reproduce: Run a compiler command under adverse
conditions as follows.
Use your own valid path to 'g++' in this command:
/MinGW-20050827/bin/g++ -E /lmi/src/lmi/about_dialog.cpp
'-E' would produce lengthy output anyway; the absence of
any '-I' pointing to wx causes error messages as well.
Cut and paste that command into two applications:
(1) 'lmi_wx_shared': "Test | Test system command"
This requires a special command-line argument:
grep durbatulûk *.?pp
(2) 'wx/samples/exec/exec': use Ctrl-O
(2) does not fail, but (1) reproduces the error: by
instrumenting the code, I determined that it attempts to
display 404732 characters in a messagebox.
|