_verified_ | Debug

A stack trace is not an error message; it is a map. It shows the exact path of function calls that led to the disaster. Read it from the bottom to the top . The bottom is where the program started; the top is where it died.

If a bug occurs when processing a 10GB JSON file, you don't debug with the 10GB file. You iteratively shrink the input. Remove half the records. Does the bug still happen? Keep shrinking until you have the smallest possible input that triggers the failure. That minimal input will directly point you to the offending data. A stack trace is not an error message; it is a map