Crash dump analysis in Visual Studio - How to choose source code location

Question

I have set up everything for debugging crash dump files but I have the problem that Visual Studio chooses the wrong source files when debugging.

The problem is that I have different source code versions of the software I want to debug:

* One version locally that I'm developing on

* Other versions that the customer is using. They are stored in a CVS repository.

So what i do is check out the code I want to use and put it in a temp directory, but Visual Studio insists on using the latest source code location.

How do I change the source code location when debugging crash dump files?

Answer 1

When I check in "Debug -> Options and Settings"  "Require source files to exactly match the original version" (used to build the executable), then there opens a File-Find DialogBox, if source-file in original path really does not match exactly the dump.
Interestingly, adding source-path to "Directories containing source code" (Solution Explorer-> Properties -> Debug Source Files) will have no effect, when source-file in original folder does match and/or above setting is unchecked. (Then my VS insists on "wrong" file).
Also, if I open needed source files from the path I want, before doing "Actions" in "Minidump File Summary" Window, then VS2010 uses the already open source-file-window, to jump into code.
But this may be a very unconvenient solution, when diving deep into call-stacks.

With kind regards

Answer 2

Put the binary files/assemblies, .pdb/symbol files and source files together, the dump file opened in Visual Studio will need to you configure the .pdb.

And we also need to ensure the Visual Studio loaded the corresponding binary files and the correct version .pdb files by the "Modules Window"[Ctrl+D,M], which only can be shown in debugging time.

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us

Answer 3

Thanks, this works well.

But for some reason I could not open the modules window in Visual Studio (2010 Professional) when debugging.  But I found a solution to this on another forum. The trick is to reset all environment settings in Tools->Import and Export Settings Wizard. Only then could i see the modules option in the Debug dropdown menu.

Answer 4

You're welcome!

Have a good day!

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us