| 1 | 9 | ||||||||||||||||||||||||
| 2 | 10 | ||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | 7 | ||||||||||||||||||||||||
1. The process of manually examining source code to identify bugs, improve code quality, and share knowledge among team members.
2. The practice of inserting messages or information into the program's output during execution for debugging or monitoring purposes.
3. A line of code that marks a specific point in the program where execution will pause for debugging purposes.
4. The process of executing a program one line or instruction at a time, allowing for detailed inspection and analysis of its behavior.
5. A statement in the code that checks if a given condition is true and throws an error if it is false, helping identify logical errors.
6. A searching algorithm that divides a sorted array or list into halves, discarding the half that's known to not contain the target element.
7. A report that displays the sequence of function calls that led to the current point of execution in a program.
8. A snapshot of a program's memory state at a particular point in time, allowing for inspection of variables and data structures.
9. A feature in debugging tools that allows programmers to monitor the value of specific variables as the program executes.
10. The process of finding and fixing errors or bugs in a program.