How can you distinguish between a global error and a local error during debugging?

Distinguishing requires careful analysis of error messages, stack traces, and system logs. Global errors often manifest as unexpected crashes, system instability, or messages indicating resource exhaustion (memory, disk space). Local errors are usually identified through specific error codes, exceptions thrown within a function, or detailed debugging information pinpointing the line of code causing the problem. Examining the context around the error is crucial.