http://bugs.winehq.org/show_bug.cgi?id=59963 Eric Pouech <eric.pouech@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #8 from Eric Pouech <eric.pouech@gmail.com> --- (In reply to Alisa Sireneva from comment #7)
On my PC, `wine repro` crashes on tip (cba7652eac8f) and works fine with the patch applied. `winedbg repro` crashes neither on tip nor with the patch (but if winedbg is started automatically after `wine repro` crashes, it does also crash on tip).
Thanks for testing. Basically, what happens is: - repro at some point catches some exception (triggered by the tests), then uses dbghelp.StackWalk to capture callstack, - dbghelp dwarf reader's thrashes memory when reading the repro dwarf's debug info, - which causes another exception, - since uncaught (or exception in exception), Wine's kernel32 launches winedbg (default registry settings) - winedbg loads dbghelp, and calls also dbghelp.StackWalk which triggers the same memory thrashing when reading repro's dwarf debug info (but in winedbg process this time) - winedbg catches this exception and quits What's "strange" is that in my yesterday testing (yet on Wine-11.0), the memory thrashing in the repro process doesn't generate a fault, while the one ine winedbg process seemt to happen always Just retested on wine's tip, and the crash happens in repro process (without the patch) Didn't chase further the root of discrenpancy, but could be different memory layout, or... Will upload the patch. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.