7

I am trying to debug a crash minidump. have the release debug symbols and release binaries same as crash.

While debugging that crash and pointing to symbols still I am getting "No matching binary found" error .

I am using the right symbols, binaries and pointing to right location.

So why this can happen? I can see a slight difference in timestamp of dll loaded in VS(9:03AM) and the release binary(9:04AM)

Can this be the reason for the error?

Any solutions for this , I need to fix the crash and since this crash occuring on client machine , I cannt repro it.

anand
  • 11,071
  • 28
  • 101
  • 159
  • Just a a guess, is it a 32bit vs 64bit issue? – Twelve47 Apr 28 '10 at 10:33
  • Yes, the timestamp should be the same of course. Review your build process and make sure you didn't copy the DLL before some kind of post-link build step, like mt.exe – Hans Passant Apr 28 '10 at 13:50
  • see http://stackoverflow.com/questions/873210/symbols-pdb-for-native-dll-are-not-loaded-due-to-post-build-step – sean e Apr 22 '11 at 06:18

1 Answers1

2

You may try to debug the dump using the windbg/ntsd (from the 'Debugging tools for Windows' package that comes with Windows SDK ). There you may try to load the symbols while ignoring a mismatch in the .pdb file versions '.reload /i' command.

vladisld
  • 528
  • 3
  • 10