https://bugs.winehq.org/show_bug.cgi?id=54159
Bug ID: 54159 Summary: kernel32:debugger - crash_and_winedbg() gets an unexpected failure count on Windows 11 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 - crash_and_winedbg() gets an unexpected failure count on Windows 11 in the 'dbg,attach,process,event,detach' case:
debugger.c:610: running dbg,attach,process,event,detach... debugger.c:621: waiting for child exit... debugger.c:198: child: crashing... debugger.c:659: waiting for the debugger... debugger.c:166: debugger traces: processing debug messages setting event done debugging... debugger.c:681: Test failed: debugger reported 4 failures
See https://test.winehq.org/data/patterns.html#kernel32:debugger
While this error is systematic on Windows 11 it never happened on Windows 10 and lower... except in MR!1823 which had something very similar:
debugger.c:600: running dbg,attach,process,event,detach... debugger.c:611: waiting for child exit... debugger.c:198: child: crashing... debugger.c:649: waiting for the debugger... debugger.c:166: debugger traces: processing debug messages setting event done debugging... debugger.c:671: Test failed: debugger reported 7 failures
https://bugs.winehq.org/show_bug.cgi?id=54159
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=54159
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |eric.pouech@gmail.com
--- Comment #1 from Eric Pouech eric.pouech@gmail.com --- both Win10 & 11 should be fixed by 17e5ff74308f41ab662d46f684db2c6023a4a16b let's wait a couple of days of testing and see what gives
https://bugs.winehq.org/show_bug.cgi?id=54159
--- Comment #2 from Eric Pouech eric.pouech@gmail.com --- (In reply to Eric Pouech from comment #1)
both Win10 & 11 should be fixed by 17e5ff74308f41ab662d46f684db2c6023a4a16b let's wait a couple of days of testing and see what gives
actually not fully solved