Symbol load broken in 6.00.0017.0 ?

When trying to debug crash dumps under the latest version of the windbg
debugger, I have found that the symbol loading mechanism seems to be
loading the first copy of any codeview symbols it encounters in the
sympath. This is, of course, causing problems because the debugger is
generating totally mismatched symbol lists.

I have tried enabling SYMOPT_EXACT_SYMBOLS and disabling
SYMOPT_NO_IMAGE_SEARCH to no avail. The debugger continues to load the
first .dbg file encountered in the symbol search path.

From what I recall, everything was working just fine under the older windbg
versions.

Has anyone experienced any problems similar to this?

Mike Hahn
xxxxx@humana.com

Use noisy symbol loading to help debug your issue. You can turn it on by adding “-n” to the command line you start the debugger with or by typeing “!sym noisy” in the debugger.

Chances are with that you will be able to determine what is going on.

-----Original Message-----
From: Mike Hahn [mailto:xxxxx@humana.com]
Sent: Mon 7/8/2002 6:05 AM
To: Kernel Debugging Interest List
Cc:
Subject: [windbg] Symbol load broken in 6.00.0017.0 ?

When trying to debug crash dumps under the latest version of the windbg
debugger, I have found that the symbol loading mechanism seems to be
loading the first copy of any codeview symbols it encounters in the
sympath. This is, of course, causing problems because the debugger is
generating totally mismatched symbol lists.

I have tried enabling SYMOPT_EXACT_SYMBOLS and disabling
SYMOPT_NO_IMAGE_SEARCH to no avail. The debugger continues to load the
first .dbg file encountered in the symbol search path.

From what I recall, everything was working just fine under the older windbg
versions.

Has anyone experienced any problems similar to this?

Mike Hahn
xxxxx@humana.com


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com