[Bug 15206] Trouble with symbolic stack dumps and Chromium

http://bugs.winehq.org/show_bug.cgi?id=15206

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #23 from Dan Kegel   2009-06-12 11:09:11 ---
Looks better -- there are line numbers now!  Here's a sample stack:

Backtrace:
=>0 0x02e49c03 DebugUtil::BreakDebugger+0x3()
[c:\users\dank\documents\chromium\src\base\debug_util_win.cc:103] in chrome
(0x0033cd14)
  1 0x01d280e8 SilentRuntimeAssertHandler+0x8(str=*** Invalid address
0x0033cd24 ***
) [c:\users\dank\documents\chromium\src\chrome\common\logging_chrome.cc:41] in
chrome (0x0033cd1c)
  2 0x02e1f1e6 logging::LogMessage::~LogMessage+0x2f6()
[c:\users\dank\documents\chromium\src\base\logging.cc:538] in chrome
(0x0033ce88)
  3 0x0341c22e ChildProcessHost::Iterator::Iterator+0x1ae(type=*** Invalid
address 0x0033d058 ***
)
[c:\users\dank\documents\chromium\src\chrome\common\child_process_host.cc:212]
in chrome (0x0033d050)
...

Two problems remain:
1) those pesky "Invalid address" notes in the arguments
2) it still takes 20 minutes to handle one backtrace

but I guess those should be filed as separate bugs.