[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: [e-mail]
        ReportedBy: [e-mail]
                CC: [e-mail]

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.