When a function within WiredTiger results in an error, it is currently hard to determine exactly from where the error came from. This is in stark contrast to languages such as Java, where the origin of an exception can be determined from the stack trace. We should implement a similar functionality in WiredTiger, in which we would keep a log of error codes processed by WT_ERR, WT_RET, and their variants, and display it if need be.