| Previous | Next |
| ERROR_STOPPED_ON_SYMLINK | ERROR_PLUGPLAY_QUERY_VETOED |
ERROR_LONGJUMP
What ERROR_LONGJUMP means
A long jump performs non-local control transfer, bypassing ordinary returns. The status is usually part of unwinding machinery rather than a user-facing failure, but it matters when debugging destructors, cleanup handlers, or corrupted stacks.
Where it appears
- setjmp/longjmp based runtimes
- language runtimes implementing non-local exits
- debuggers and crash analyzers observing exception dispatch
Likely causes
- an intentional longjmp call
- runtime implementation of cancellation or error escape
- stack corruption falsely resembling a valid jump context
What to collect
- jump origin and destination stacks
- saved jump-buffer contents and owning thread
- resources acquired between setjmp and longjmp
- compiler, runtime, and exception model
How to respond
For intentional use, ensure every skipped resource has an explicit cleanup strategy; C++ objects with automatic destructors make raw longjmp especially dangerous. For unexpected occurrences, capture a dump and inspect stack integrity rather than retrying the operation.
References
Looking for a different code? Search another status or error code.