http://bugs.winehq.org/show_bug.cgi?id=16471
--- Comment #34 from Mikko Rönkkö mikko.ronkko@iki.fi 2010-06-18 07:53:43 --- I did some testing and this seems to be related to file writing. The software opens a file for output, but seems to crash when it tries to write to this file.
I am attaching results of running the 5.1 and 6 versions of the software with WINEDEBUG=+relay
The 6.0 version first prints six lines to screen and then crashes when it tries to write to the output file. I assume that these 7 lines are 6 lines to stdout and one failed write attempt to the results file.
0009:Call KERNEL32.WriteFile(00000008,04597808,00000002,045195a0,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(00000008,04597808,00000016,045195a0,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(00000008,04597808,00000016,045195a0,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(00000008,04597808,00000002,045195a0,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(00000008,04597808,00000027,04519580,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(00000008,04597808,00000002,04519580,00000000) ret=01444789 0009:Call KERNEL32.WriteFile(0000000c,04517be0,000003ab,04517bc0,00000000) ret=014b96ce
The 5.1 version prints first 6 lines of header and 1 error message line to stdout and 22 lines to the results file.
0009:Call KERNEL32.WriteFile(00000008,042a7950,00000002,04229954,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000008,042a7950,00000018,04229954,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000008,042a7950,00000016,04229954,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000008,042a7950,00000027,04229934,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000008,042a7950,00000002,04229934,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000013,04229514,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000011,04229524,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000016,04229514,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,042291b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000014,04229144,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,042291b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,042291b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000058,042b0100,0000005c,04198844,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000058,042b0100,0000005e,04198844,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000058,042b0100,0000005e,04198844,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,0000001b,04199334,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000045,04199334,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000014,04199334,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(00000008,042a7950,0000002d,04199434,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,041992b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,041992b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000011,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000012,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000018,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,041992b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000015,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000015,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000018,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000020,04199204,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000002,041992b4,00000000) ret=011c5749 0009:Call KERNEL32.WriteFile(0000003c,042abdc0,00000029,04199204,00000000) ret=011c5749
The one error line in the 5.1 output is due to using empty analysis file and is part of the correct behavior of the software.
Since the error occurs during writing of the results file header, which is unrelated to the analysis results, my guess is that the bug is related to file writing.
The proper component for this is probably NTDLL, but I could be wrong.