http://bugs.winehq.org/show_bug.cgi?id=18274
--- Comment #4 from Anastasius Focht focht@gmx.net 2009-05-20 15:14:21 --- Hello,
thanks, fixed by commit d5d0738fb9f87f2c01c172d1653158444f520efa
--- snip --- ... 0009: create_mapping( access=00000006, attributes=00000000, protect=00000043, size=003d6000, file_handle=0000, objattr={rootdir=0000,sd={},name=L""} ) 0009: create_mapping() = 0 { handle=0054 } ... 0009:trace:virtual:NtMapViewOfSection handle=0x54 process=0xffffffff addr=(nil) off=000000000 size=0 access=4 0009: get_mapping_info( handle=0054, access=00000002 ) 0009: get_mapping_info() = 0 { size=003d6000, protect=67, header_size=0, base=00000000, mapping=0060, shared_file=0000 } 0009: get_handle_fd( handle=0054 ) 0009: *fd* 0054 -> 28 0009: get_handle_fd() = 0 { type=1, removable=0, access=00000006, options=00000020 } 0009:trace:virtual:map_view got mem in reserved area 0xe50000-0x1226000 0009:trace:virtual:VIRTUAL_DumpView View: 0xe50000 - 0x1225fff (anonymous) 0009:trace:virtual:VIRTUAL_DumpView 0xe50000 - 0x1225fff c-rw- 0009:trace:virtual:create_view forcing exec permission on 0xe50000-0x1225fff 0009:trace:virtual:NtMapViewOfSection handle=0x54 size=3d6000 offset=000000000 0009:trace:virtual:NtProtectVirtualMemory 0xffffffff 0x400000 003da000 00000040 0009:trace:virtual:VIRTUAL_SetProt 0x400000-0x7d9fff c-rwx 0009:trace:virtual:VIRTUAL_DumpView View: 0x400000 - 0x7e9fff 0x20 0009:trace:virtual:VIRTUAL_DumpView 0x400000 - 0x7d9fff c-rwx 0009:trace:virtual:VIRTUAL_DumpView 0x7da000 - 0x7dffff c---- 0009:trace:virtual:VIRTUAL_DumpView 0x7e0000 - 0x7e9fff c-r-- 0009: close_handle( handle=0060 ) 0009: close_handle() = 0 0009:trace:virtual:NtFreeVirtualMemory 0xffffffff 0xff8e0000 003e0000 4000 0009: close_handle( handle=0054 ) 0009: close_handle() = 0 ... --- snip ---
Regarding the follow up bug (comment #3) it seems the download has changed and I get now a different result (which is another bug i've already seen but not filed yet). Most likely different flavours of this Xenocode appliance.
Please mark it FIXED - even if the app displays a crash dialog now. This specific problem is resolved and follow up issues are tracked separately.
Regards