debugging - Using windbg for the first time to debug a process which shuts down without warning -


I have a process, when I click on a button on my UI, another process launches this In the process it stops any clues without any warning or logs.

How do I use the Windbug to understand this problem? Also, what do I do for the symbol file path? To download symbols from MS symbols, I am not sure that I have to set an NV variable too.

Thanks

How to get symbols here:.

Generally, the easiest way to do this is to set an environment variable:

  _NT_SYMBOL_PATH = SRV * c: \ websymbols * Http: //msdl.microsoft .com / download / symbols  

Be sure that after you set environment variables, you start Windbg, and keep in mind that VS Recent versions of this will also use this environment variable, so they will be slow to start debugging.

My first step will try to do two processes and will separate - can you start the one who fails, as if it fails?

Quit Often one of these indicates:

  • One stack overflow (infinite recursion)
  • Exception in an exception handler (sometimes)
  • Messing with the main window setup sequence in the WPF app.

Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -