A horror novelist converted error handling to Lovecraftian cosmic dread because stack traces should inspire existential terror. The system speaks in cosmic horror metaphors that somehow perfectly describe programming failures while the Old Ones whisper debugging advice from R'lyeh. Your task: Interpret stack traces written by tentacled horrors who think segmentation faults are divine punishment.
Why You're Doing This
This tests pattern recognition in natural language, error classification, and maintaining semantic meaning through metaphorical translation. You're building a system that maps abstract horror concepts to concrete technical problems.
Take the W
✓ Maps Lovecraftian terminology to standard programming errors
Ia! Ia! The void hungers for your pointers and finds only nothingness! → NULL_POINTER_EXCEPTION - Attempted to dereference null pointer
Input Format:
Lovecraftian error string with embedded technical markers
Expected Output:
Structured error object with horror-to-technical mapping
Example:
The ancient ones whisper of stack overflow in the cyclopean depths → {"error_type": "STACK_OVERFLOW", "location": "recursive_function", "horror_level": "cyclopean"}