| 1 | 4 | ||||||||||||||||||||||||
| 5 | 7 | ||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 2/3 | |||||||||||||||||||||||||
1. The process of manually examining source code to identify bugs, improve code quality, and share knowledge among team members.
2. A searching algorithm that divides a sorted array or list into halves, discarding the half that's known to not contain the target element.
3. A line of code that marks a specific point in the program where execution will pause for debugging purposes.
4. The process of finding and fixing errors or bugs in a program.
5. A snapshot of a program's memory state at a particular point in time, allowing for inspection of variables and data structures.
6. 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.
7. A feature in debugging tools that allows programmers to monitor the value of specific variables as the program executes.
8. A report that displays the sequence of function calls that led to the current point of execution in a program.