Software Troubleshooting and Error Types

Study Notes

Identifying and resolving problems or faults in software or computer systems.
Often involves locating and fixing "bugs" or errors that affect a program's behavior.

Occur during the compilation process when the compiler cannot understand the code.
Typically due to syntax errors where the code doesn't adhere to the programming language's rules.
Examples include missing semicolons, extra brackets, or incorrect keywords.
Must be fixed before the code can be compiled.

Don't prevent compilation, but can signal potential runtime or logic errors.
Should not be ignored, as they often indicate problems that might not be obvious later.

Occur during the linking stage of the compilation process.
Indicate that the code compiles but functions, libraries, or global variables it uses are declared but not defined correctly.

Occur during the execution of the program.
Can be triggered by various factors such as incorrect user input, hardware failures, resource limitations (memory, disk space), network connection problems, or certain mathematical operations (e.g., division by zero).

Local Debugging: Debugging within a specific area of code (e.g., a function).
Remote Debugging: Debugging code running on a separate machine from where the debugger is located.
Breakpoints: Points set in the code where program execution pauses, allowing inspection of variables and program state.
Trace Output: Adding temporary code (e.g., print statements) to display the values of variables or program flow for debugging purposes.
Dump Files: Creating files containing snapshots of the program's memory or state at specific points.
Log Files: Storing events, actions, or errors that happen during program execution in a file for analysis.

Compiling: Use Build Solution (for new programs) or Rebuild Solution (for programs already compiled).
Running and Debugging: Start debugging using **Debug  Start Debugging ** or by clicking the green "play" button.
Step-by-Step Execution: Use Debug  Step Into (F11) to execute one line at a time, and then use Debug  Step Over (F10) to step over the next line. The yellow arrow indicates the next line to be executed.
Monitoring Variables: Use Debug  Windows  Watch  Watch 1 (or 2/3/4) to open the Watch window. Enter the names of variables you want to monitor.
Stopping Execution: Use Debug  Stop Debugging to stop the program's execution.