[Bug 18943] New: Winedbg prints "illegal address" a lot during backtraces of chromium unit test crashes
http://bugs.winehq.org/show_bug.cgi?id=18943 Summary: Winedbg prints "illegal address" a lot during backtraces of chromium unit test crashes Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com CC: eric.pouech(a)orange.fr In bug 15206, I mentioned that windbg output "illegal address" often during backtraces of chromium unit tests when getting symbols from .pdb's, e.g. Backtrace: =>0 0x02e49c03 DebugUtil::BreakDebugger+0x3() [c:\users\dank\documents\chromium\src\base\debug_util_win.cc:103] in chrome (0x0148e17c) 1 0x01d280e8 SilentRuntimeAssertHandler+0x8(str=*** Invalid address 0x0148e18c *** ) [c:\users\dank\documents\chromium\src\chrome\common\logging_chrome.cc:41] in chrome (0x0148e184) 2 0x02e1f1e6 logging::LogMessage::~LogMessage+0x2f6() [c:\users\dank\documents\chromium\src\base\logging.cc:538] in chrome (0x0148e2f0) 3 0x025135fa ExtensionMessageService::RendererShutdown+0xea(renderer=*** Invalid address 0x0148e410 *** This seems wrong, and is fairly annoying. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=18943 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #1 from Anastasius Focht <focht(a)gmx.net> 2011-05-29 09:02:36 CDT --- Hello, most likely the process has been forcibly terminated by outside and winedbg still tries to access/interpret now unmapped address space. If that still happens you need to find out who might forcibly kill tests/processes when the crash handler (winedbg) is already attached and working on the target. Maybe some timeout (=> kill test) is interfering when the crash handler takes too long to collect backtrace info. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=18943 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh(a)gmail.com --- Comment #2 from Jerome Leclanche <adys.wh(a)gmail.com> 2011-11-02 17:35:44 CDT --- What happened to this? Does it still happen? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
https://bugs.winehq.org/show_bug.cgi?id=18943 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, no further response from OP, resolving 'abandoned'. Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=18943 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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.
participants (1)
-
wine-bugs＠winehq.org