Connect WinDbg to start the process from HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Run at login?

Question

I have a .NET application deployed to 28,000 workstations currently. In all cases, this process starts when a user logs in from a registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. On most of these workstations, it works fine, but on some, it will work when launched this way. Annoyingly, launching it manually after the login is working fine and no crashes occur.

So, I'm trying to figure out how to bring WinDbgand connect to this process over time, try to get a memory dump and at least some idea of ​​what is going on.

How can i do this? As far as I know, the order of automatic launch of applications is not guaranteed in Windows (this is WindowsXP SP3, if that matters), and therefore it will not be very simple.

Answer 1

One way to do this is with GFlags . Gflags may be instructed to connect to the debugger when the process starts.

And a script debugger can be passed on the command line to get a memory dump when the process terminates or throws an exception.

Answer 2

, . Debugger.Break(), JIT .

, WinDbg JIT , , .