Summary
This chapter covers using exception stack traces to read and interpret the chain of method calls and pinpoint where runtime errors occur in code.

General domain of usage
Software debugging

When you run into an exception in your code, the error message that appears in the console often includes a stack trace. A **stack trace** is a list of method calls that the program was executing when the exception occurred. This list shows you exactly where the error happened, and the path the code took to get there. Learning to read stack traces is a crucial skill for debugging, because they point you directly to the source of a problem.

A **stack trace** is a report that shows the sequence of method calls leading up to an exception. It helps you trace the flow of execution and quickly identify where things went wrong.

Definition

dXNpbmcgU3lzdGVtOwoKbmFtZXNwYWNlIENvbnNvbGVBcHAKewogICAgcHVibGljIGNsYXNzIFByb2dyYW0KICAgIHsKICAgICAgICBwdWJsaWMgc3RhdGljIHZvaWQgTWFpbihzdHJpbmdbXSBhcmdzKQogICAgICAgIHsKICAgICAgICAgICAgdHJ5CiAgICAgICAgICAgIHsKICAgICAgICAgICAgICAgIENhdXNlRXJyb3IoKTsKICAgICAgICAgICAgfQogICAgICAgICAgICBjYXRjaCAoRXhjZXB0aW9uIGV4KQogICAgICAgICAgICB7CiAgICAgICAgICAgICAgICBDb25zb2xlLldyaXRlTGluZSgiQW4gZXhjZXB0aW9uIG9jY3VycmVkOiIpOwogICAgICAgICAgICAgICAgQ29uc29sZS5Xcml0ZUxpbmUoZXguVG9TdHJpbmcoKSk7CiAgICAgICAgICAgIH0KICAgICAgICB9CgogICAgICAgIHB1YmxpYyBzdGF0aWMgdm9pZCBDYXVzZUVycm9yKCkKICAgICAgICB7CiAgICAgICAgICAgIGludCBudW1iZXIgPSBpbnQuUGFyc2UoIm5vdCBhIG51bWJlciIpOwogICAgICAgIH0KICAgIH0KfQo=

When you run this code, it throws a `FormatException` because `"not a number"` cannot be converted to an integer. The output includes a stack trace, which lists each method that was called before the error happened. You will see something like this:

```
System.FormatException: Input string was not in a correct format.
   at System.Number.ThrowOverflowOrFormatException()
   at System.Int32.Parse(String s)
   at ConsoleApp.Program.CauseError() in C:\...\Program.cs:line 17
   at ConsoleApp.Program.Main(String[] args) in C:\...\Program.cs:line 10
```

The stack trace starts with the most recent method call, which is where the exception occurred, and works backwards through the chain of calls that led there. Here, you can see that `int.Parse` failed, which was called inside `CauseError`, which was called by `Main`. The file and line numbers help you jump straight to the problem in your code.

What information does a stack trace provide?

Master the art of robust C# programming by learning how to handle, create, and debug exceptions. This hands-on course guides you through real-world error handling scenarios, from basic try-catch to custom exceptions and safe file operations.

Learn the basics of exceptions in C#, how to use try-catch blocks, and why error handling is crucial for robust applications.

Learn to create your own exception types and use guard clauses to prevent invalid states in your code.

Master techniques for validating user input and safely parsing data to prevent runtime errors.

Handle file operations safely and learn to debug exceptions using stack traces and refactoring techniques.

Debugging Exception Stack Traces

1. What information does a stack trace provide?

2. How can stack traces help you fix bugs?