Foundational unit of the BugSplat universe. BugSplat client libraries integrate with your code to capture exception information and send it to the BugSplat website. This package of information is called a crash report.
The active subroutines of your program at some point in time. In the BugSplat world, that time is typically the time of a crash. The call stack identifies which subroutines have been called in what order. The call stack is also known as the stack trace, execution stack, program stack, or simply the stack.
The stack key is BugSplat term for a specific function in a call stack. The stack key is used to group similar crash reports. The default stack key is the function at the top of the call stack. However, crash reports can be grouped by different levels too. See our sub key page for additional details on this.
One level of the call stack.
An anomalous or exceptional condition requiring special processing during computation.
Exception that has logic to mitigate an error scenario such as to display a dialog to the user or reset values to their defaults. A program can continue execution after a handled exception.
Unexpected exception where the surrounding code does not have logic to handle the scenario and can put the program into an unknown state
Logic to mitigate an error scenario and resume program execution or to capture forensic data for post mortem analysis and exit program.
File that contains program state such as call stack, register values, loaded modules and system information. In many environments, BugSplat creates a minidump file automatically at the time of a crash.
Files that contain information to map information in the minidump file to file names and line numbers in source code.