Home/ Questions/Q 3243656
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T18:27:33+00:00

Summary of Answers To avoid the debugger trapping Ctrl+C first turn off the Visual

  • 0

Summary of Answers

To avoid the debugger trapping Ctrl+C first turn off the Visual Studio
Hosting Process (found in project properties, Debug tab)

If you’re using the Express version of Visual Studio, that’s all you
can do.

If you’re using the Pro or better version of Visual Studio you can
additionally open Debug > Exceptions…, Win32 Exceptions, and uncheck
Ctrl+C.

As as alternative, you can use Ctrl+Break when debugging, unless like me Ctrl+C is hard-wired into your brain.

Original

The following has been edited. Hans seems to have retracted his answer, but his questioning has helped me to narrow down the problem statement:

Extra Clarity

  • I do not want to modify the behavior of Ctrl+C.
  • I’m not looking for a work around.
  • I simply want the debugger to NOT break when Ctrl+C is pressed during a debugging session.

Please note that the following example is contrived. It’s just to demonstrate the behavior. I changed the ReadKey line as it was distracting people.

Debug (run) the following program:

class Program
{
    static void Main()
    {
        System.Threading.Thread.Sleep(System.Threading.Timeout.Infinite);
    }
}

Press Ctrl+C. The debugger will break as if you set a breakpoint on the Sleep line.

How do you turn this off? I don’t want the debugger to break at all for Ctrl+C.

This doesn’t happen at home with VS2008 Pro.

I have now tried it with both VS2008 Express and VS2010 Express (the only editions I can test it with easily) and they all do it. This has led me to believe that either it’s an Express behavior, or that there is a setting somewhere to toggle it on/off.

  1. Is there a setting to turn this on/off in any version/edition?
  2. Does this setting exist in VS2008, VS2010, or both?
  3. Is the setting exposed in the Express editions?
  4. Is my instance of VS2008 Pro unique? Is the setting something that was exposed in an old version of Visual Studio that has carried over (I have carried over VS settings through many new versions).
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I found the answer, it is a debugging Exception option. I don’t know how I missed it the first time, but here it is:

    Debug -> Exceptions… Win32 Exceptions – Control-C

    This is in VS2008 Pro.

    I can also confirm that the option does NOT exist in the Express editions (the entire Win32 Exceptions node is missing).

    So the only question I have left, since I don’t own VS2010 Pro (yet?) is: Does the Win32 Exceptions node, and the Control-C exception exist in the VS2010 Pro edition?

    • 0