Adding “-n” to the command line of any of the debuggers that ship in the
package will turn on noisy symbol loading. It’s a tad bit easier to
type than -sflags…
-----Original Message-----
From: Tony Mason [mailto:xxxxx@osr.com]
Sent: Thursday, March 14, 2002 3:27 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Setup Win XP host and Win 2000 target?
Try using the command “!sym noisy” - this will show you where the
debugger is searching for symbols.
You can also achieve the same thing by starting WinDBG with the “-sflags
0x80030237” option (see the documentation for a description of the
various symbol options).
Of course, you can always try the current version of the debugger as
well - the current version is 6.0.7.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@softek.dk [mailto:xxxxx@softek.dk]
Sent: Thursday, March 14, 2002 5:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Setup Win XP host and Win 2000 target?
I am not too experienced in windbg and need some help.
After updating the system to Windows XP with Visual Studio .NET and
windbg 4.00.18 I have trouble getting the debug session to run.
The symbol path is set to the win 2000 symbol directory installed on the
host.
After a series of ModLoad og XP ddls the debugger stops with:
*** WARNING: symbols timestamp is wrong 0x3b7de01e 0x3af32050 for
ntdll.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntdll.dll -
ntdll!DbgBreakPoint:
77f7f570 cc int 3
Thanks
Henrik Bech
You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%