Debuggers don't kick in when application crashes

Question

I am trying to debug an application with Immunity debugger. I also tried WinDbg. I have set them as default JIT debugger through the Registry but it doesn`t work.

I tried in Windows XP SP3 and in Windows 7 but it doesn't work.

possible duplicate of http://stackoverflow.com/questions/30457570/windows-does-not-produce-full-crash-dumps-even-though-registry-is-set-correctly/30469083#30469083 — Thomas Weller, Jul 01 '15 at 21:18

score 3 · Answer 1 · answered Mar 22 '20 at 08:47

This might help someone whose immunity debugger does not kick in when the application really crashes like mine.

In regedit, edit the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

Default: (value not set)
Auto: 1
Debugger: "C:\Program Files\Immunity Inc\Immunity Debugger\ImmunityDebugger.exe" -p %ld
UserDebuggerHotKey: 0

score 1 · Accepted Answer · edited May 23 '17 at 12:29

1

You can install Windbg as the default postmortem debugger by running this from the command line:

windbg -IS

From then on, the next time an application crashes Windbg will appear, attached to the process.

To undo this, see this answer.

If this doesn't work, you'll need to add more details to your question.

edited May 23 '17 at 12:29

Community

1
1

answered Jul 01 '15 at 15:38

Patrick Quirk

23,334
2
57
88

It was my failure. The application did not crash but I thought that it crashed. Thanks for your help. – Eduard Hasanaj Jul 02 '15 at 00:49

score 0 · Answer 3 · answered Oct 11 '20 at 10:14

0

If you are using Immunity Debugger, you may want to try to install python 2.7 on your PC. If it is already installed try reinstalling it

answered Oct 11 '20 at 10:14

kavishka gihan

1

Debuggers don't kick in when application crashes

3 Answers3