Exception Handling and Debugging Techniques

These flashcards cover essential terminology and concepts related to exception handling and debugging in programming.

Debugging

The process of identifying and rectifying errors in a program that leads to unexpected behavior.

Error Symptoms

Manifestations of issues in code such as crashes, error messages, or unexpected behaviors.

Backtracking

A debugging technique that involves tracing back the code from the point that the problem first occurred.

Breakpoints

Defined points in code where execution is temporarily halted, allowing for inspection of the program's state.

Binary Search in Debugging

A technique to narrow down the location of bugs by dividing the problem space and isolating components.

Rubber Ducking

Explaining a problem out loud or in writing to clarify thinking and identify solutions.

Log Analysis

The use of logging statements to understand code execution flow and variable values for debugging.

IOException

The base class for exceptions thrown while accessing data from files, directories, and streams.

ArithmeticException

An exception raised whenever an invalid mathematical operation occurs, such as dividing by zero.

try block

A block of code where programmers can 'try' a procedure that might cause an error.

catch block

A segment of code that handles exceptions thrown by a preceding try block.

finally block

A block of code that executes after try-catch sequences, regardless of whether an exception occurred.

Error Class

Represents serious errors from which a program usually cannot recover.

Exception Class

Represents less serious errors that indicate unusual conditions and from which a program can recover.

Stack Trace

A list of error messages showing the method calls that were in progress at the time of an error.

InputMismatchException

Occurs when the user does not provide the proper type of input or input is out of range.

OutOfMemoryError

Thrown when there is insufficient space to allocate an object.

VirtualMachineError

Indicates that the Java Virtual Machine is broken or has run out of resources to continue operating.