Home/ Questions/Q 1113869
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T02:55:16+00:00

Folks, Debugging a .net 4.0 app using WinDbg (I’m a beginner to WinDbg). I’m

  • 0

Folks,

Debugging a .net 4.0 app using WinDbg (I’m a beginner to WinDbg). I’m trying to break when I hit a stack overflow:
(NTSTATUS) 0xc00000fd – A new guard page for the stack cannot be created

Unfortunately, this overflow happens about 2-hours into a long-running process and logs tells me that it doesn’t always happen at the same time/place. If I attach to the process in the debugger, the program runs terribly slow…it might take a few days to hit the bug! Is there a way to speed up the app/WinDbg by telling WinDbg to ONLY break for this particular error?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can instruct ADPLus to create dumps of the process when exceptions occur. John Robbins has a good article on the subject. You can then use WinDbg to debug the dump file(s).

    Be aware, that the original adplus.vbs has been replaced by adplus.exe, which is supposed to provide the same functionality. In my experience there are a few problems with the new implementation, so you may need to use the old script, which is still available as adplus_old.vbs.

    • 0