I am a .NET programmer who is starting to dabble into C . In C# I would put the root function in a try catch, this way I would catch all exceptions, save the stack trace, and this way I would know what caused the exception, significantly reducing the time spent debugging.

But in C some stuff(access violation, divide by zero, etc.) are not caught by try catch. How do you deal with them, how do you know which line of code caused the error?

For example let's assume we have a program that has 1 million lines of code. It's running 24/7, has no user-interaction. Once in a month it crashes because of something that is not caught by try catch. How do you find out which line of code caused the crash?

Environment: Windows 10, MSVC.

CodePudding user response：

C is meant to be a high performance language and checks are expensive. You can't run at C speeds and at the same time have all sorts of checks. It is by design.

Running .Net this way is akin to running C in debug mode with sanitizers on. So if you want to run your application with all the information you can, turn on debug mode in your cmake build and add sanitizers, at least undefined and address sanitizers.

For Windows/MSVC it seems that address sanitizers were just added in 2021. You can check the announcement here: