Finding the right symbols

I have a minidump from a user of an application failure. The user tells me
he is on W2K, but isn’t able to determine the patch level or anything else
detailed.

The stack traceback goes into MFC42.dll, and WinDbg can’t manage to resolve
the symbols for this, despite being set up for the MS webserver. So it
falls back to the export symbols, which are virtually useless since I’m
something like 10 calls deep in MFC42 when it crashes with a null pointer.

I’ve tried the three versions of debug symbols that I happen to have lying
around for MFC42, and they are all three obviously completely wrong, so are
no help at all. None of them even seems to come close to being real.

Does anyone know of any way to try to track down the right symbols for an MS
dll when the web symbol server refuses to try to do the resolution? If I
could just somewhere find a directory or list of all of the possible
US-english versions of MFC42 I could keep trying them until I found one that
seemed close.

Thanks,

Loren

If I understand correctly, it is only 64KB, the minidump, so there is no way
to list the lm(loaded modules) !.
If it were then probably the build time might help to track down. Also w2k
with what service packs ?. Maybe someone has the CD somewhere lying around,
and the symbols might be available from there, but MFC42 sounds like very
old, NT4.0 time frame, so vc4.2 might be another place to shoot for !!!

-pro

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Loren Wilton
Sent: Thursday, June 03, 2004 6:24 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Finding the right symbols

I have a minidump from a user of an application failure. The user tells me
he is on W2K, but isn’t able to determine the patch level or anything else
detailed.

The stack traceback goes into MFC42.dll, and WinDbg can’t manage to resolve
the symbols for this, despite being set up for the MS webserver. So it
falls back to the export symbols, which are virtually useless since I’m
something like 10 calls deep in MFC42 when it crashes with a null pointer.

I’ve tried the three versions of debug symbols that I happen to have lying
around for MFC42, and they are all three obviously completely wrong, so are
no help at all. None of them even seems to come close to being real.

Does anyone know of any way to try to track down the right symbols for an MS
dll when the web symbol server refuses to try to do the resolution? If I
could just somewhere find a directory or list of all of the possible
US-english versions of MFC42 I could keep trying them until I found one that
seemed close.

Thanks,

Loren


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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