https://bugs.winehq.org/show_bug.cgi?id=53144
Bug ID: 53144 Summary: kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7:
debugger.c:2122: Test failed: NtSetInformationDebugObject failed c0000008 debugger.c:2144: Test failed: NtSetInformationDebugObject failed c0000008
https://test.winehq.org/data/patterns.html#kernel32:debugger
0xc0000008 == STATUS_INVALID_HANDLE
Sometimes only the second failure happens.
https://bugs.winehq.org/show_bug.cgi?id=53144
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=53144
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|kernel32:debugger - |kernel32:debugger - |test_kill_on_exit() |test_kill_on_exit() |sometimes fails on Windows |sometimes fails on Windows |7 |
--- Comment #1 from François Gouget fgouget@codeweavers.com --- This also happened on Windows 10 1909 on 2022-05-05 and 2022-07-05, both times with w1064v1909-64.
https://bugs.winehq.org/show_bug.cgi?id=53144
--- Comment #2 from François Gouget fgouget@codeweavers.com --- This also happens on Windows 10 21H1 (2022-12-09 w10pro64-64).
https://bugs.winehq.org/show_bug.cgi?id=53144
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@gmail.com
--- Comment #3 from Eric Pouech eric.pouech@gmail.com --- trying to look into it.
basically, the test does: 1) create a thread 2) create a debug port object attached to that thread 3) terminate that thread 4) and check status of debug port after thread termination
the test makes the assumption that the debug object is not destroyed after thread forces termination
but: - the sporadic failures reported in this report show that it's not always the case (the error status code suggests that the debug object handle is no longer valid) - more interestingly, adding some delay between steps 3 & 4 above seems to increase the number of failures (see https://testbot.winehq.org/JobDetails.pl?Key=129708)
so it rather looks like the assumption about the test is wrong, and the debug object is always destroyed upon thread termination, perhaps waiting for debuggee termination (requires further investigation)
-
WineHQ Bugzilla