changing binary path in a crashdump in Visual C++ 2008

[Jonathan Wilson]

I get crashdumps from users (standard minidumps).
Some of the users have installed the program generating the crashdumps in a
folder other than the default. In some cases its in a folder such as g:\app
(or similar) where g:\ is a drive letter I dont even HAVE.
Is there a way to tell Visual C++ where to look for the binaries so it
doesn't try (and fail) to load the app binary from the non-existant path?

[Geoff]

On Wed, 28 Oct 2009 21:46:13 +0900, Jonathan Wilson

Post by Jonathan Wilson
I get crashdumps from users (standard minidumps).
Some of the users have installed the program generating the crashdumps in a
folder other than the default. In some cases its in a folder such as g:\app
(or similar) where g:\ is a drive letter I dont even HAVE.
Is there a way to tell Visual C++ where to look for the binaries so it
doesn't try (and fail) to load the app binary from the non-existant path?

Doing "subst g: c:\path_to_your_app" in a cmd shell will redirect your
stuff, seems to work immediately in all windows shells including
explorer, I have not tried it in the debugger. Not sure if it will
work if they renamed your app folder.

[Geoff]

On Wed, 28 Oct 2009 21:46:13 +0900, Jonathan Wilson

Post by Jonathan Wilson
I get crashdumps from users (standard minidumps).
Some of the users have installed the program generating the crashdumps in a
folder other than the default. In some cases its in a folder such as g:\app
(or similar) where g:\ is a drive letter I dont even HAVE.
Is there a way to tell Visual C++ where to look for the binaries so it
doesn't try (and fail) to load the app binary from the non-existant path?

Doing "subst g: c:\path_to_your_app" in a cmd shell will redirect your
stuff, seems to work immediately in all windows shells including
explorer, I have not tried it in the debugger. Not sure if it will
work if they renamed your app folder.