http://bugs.winehq.org/show_bug.cgi?id=20676
--- Comment #2 from Peter Urbanec bugzilla.winehq.org@urbanec.net 2009-11-12 08:52:42 --- Not quite sure what you mean by "Terminal output?"
WinDbg is a GUI application, however it does open a text window. I have pasted the messages that are output in that WinDbg window.
I've repeated the test with cdb.exe and the CLI output is almost identical:
------------
E:>"C:\Program Files\Debugging Tools for Windows\cdb" -z notepad.dmp
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\notepad.dmp] User Mini Dump File: Only registers, stack and portions of memory are available
Dir entry 1, ThreadListStream stream stream size mismatch (0x300 != 0x34) WARNING: Minidump contains unknown stream type 0xfff0 Symbol search path is: symsrv*symsrv.dll*c:\localcache*http://msdl.microsoft.com /download/symbols Executable search path is: Windows XP Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer Debug session time: Thu Nov 12 20:03:40.000 2009 (GMT+11) System Uptime: not available Process Uptime: not available ERROR: Reload failure, partially initialized target WaitForEvent failed, HRESULT 0x8000FFFF "Catastrophic failure" When WaitForEvent fails on dump files the current state is not displayed. If you are having symbol problems you will need to restart the debugger after you correct the symbol path. .restart can also be used. ?:???>