http://bugs.winehq.org/show_bug.cgi?id=2813
------- Additional Comments From burnus@gmx.de 2005-05-04 13:43 ------- Created an attachment (id=833) --> (http://bugs.winehq.org/attachment.cgi?id=833&action=view) WINEDEBUG=+relay,+edit
I did with a recent CVS build of Wine the following, knowing (see comment above) that the edit.c patch causes the crash.
WINEDEBUG=+edit,+combo ~/bin/origin trace:edit:EditWndProc_common hwnd=0x10088 msg=c wparam=0 lparam=4132c3f0 trace:edit:EDIT_WM_SetText L"10" trace:edit:EDIT_EM_ReplaceSel L"10", can_undo 0, send_update 0 trace:edit:EDIT_EM_ReplaceSel inserting stuff (tl 0, strl 2, selstart 0 ('L""'), text 'L""') trace:edit:EDIT_EM_ReplaceSel notification EN_MAXTEXT sent to hwnd=0x10084 trace:combo:ComboWndProc_common [0x10084]: msg WM_COMMAND wp 050103e9 lp 00010088 wine: Unhandled exception (thread 000b), starting debugger... WineDbg starting on pid 0xa Unhandled exception: page fault on write access to 0x000000b4 in 32-bit code (0x406f1315). In 32 bit mode.
WINEDEBUG=+relay,+edit ~/bin/origin 2>&1 |grep -A100000 EN_MAXTEXT |grep -vE 'ntdll.RtlImageRvaToVa|ntdll.NtReadVirtualMemory|kernel32.ReadProcessMemory'
The top lines of that output can be find in the attached file.