http://bugs.winehq.org/show_bug.cgi?id=20895
Summary: Invalid write in DIALOG_CreateIndirect after evil dialog destroys itself in WM_INITDIALOG Product: Wine Version: 1.1.33 Platform: PC OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
http://kegel.com/wine/valgrind/logs/2009-11-05-09.09/vg-user32_dialog.txt shows Invalid write of size 4 at DIALOG_CreateIndirect (dialog.c:701) by DialogBoxParamA (dialog.c:840) by test_DialogBoxParamA (dialog.c:960) by func_dialog (dialog.c:1157) by run_test (test.h:535) by main (test.h:585) Address 0x7f040428 is not stack'd, malloc'd or (recently) free'd Error still there as of last run, http://kegel.com/wine/valgrind/logs/2009-11-30-19.16/vg-user32_dialog.txt
The test is a gnarly situation: "a dialog which destroys itself on WM_INITDIALOG"
How bulletproof are we supposed to be in that situation?