Is there way to change executable path when debugging crashdumps?

Question

While trying to debug minidumps of our application taken during crashes on customer PCs, I find that the path where they install the application seem to have an effect on where my executable should be installed for debugging.

For example, if user installed in some location "N:\AppFolder", I'm forced to create a drive with letter "N" and "AppFolder" and install my application before debugging the application. Other wise I get a error saying module cannot be found. Is there a way to select arbitrary location of executable or module while debugging crash dumps ?

Environment: Visual studio 2010, Windows 7 crashdumps are of type minidump.

Answer 1

As described by Microsoft, open the immediate window and type .exepath to change it.

Answer 2

I use the Windows Error Reporting system to receive .cab files containing crash dump files. I use Visual Studio to process the dump files and I do not have to recreate the user environment to process the dump file. My only requirement is to copy the dump file to my locally installed copy of the software that the user has installed. I do not need to use the same naming conventions the user has specified. I then make sure my symbol files are pointing to the appropriate cache and start debugging. This methodology works for Visual Studio or WinDbg.