This (static) page lets you see what the error.log file stores when a servlet crashes.
When G-WAN is not running as a daemon, the Terminal is also listing crash reports
-making it easier to develop your C scripts.
All the line numbers of the function calls that lead to the crash are listed, along with
the query to let you duplicate the problem and find the bug.
Knowing the client IP address may help blacklist unwanted visitors (the kind that
attempts to abuse).
Crash reports are not sent to clients (crashing servlets just return "500: Internal
server error" until the bug is fixed).
----------------------------------------
Exception : c0000005 Write Access Violation
Address : 01271d1f
Access Address: 00000000
Registers : EAX=0badc0de CS=001b EIP=01271d1f EFLGS=00010206
EBX=01271d4d SS=0023 ESP=014aefd4 EBP=014aefd4
ECX=00000000 DS=0023 ESI=fb181d46 FS=003b
EDX=014af9f4 ES=0023 EDI=fb181d46 CS=001b
Call Chain :(line) PgrmCntr(EIP) RetAddress FramePtr(EBP) StackPtr(ESP)
crash(): 29 01271d1f 01271d5c 014aefd4 014aefd4
main(): 39 01271d5c 0041631e 014aefdc 014aefd4
Servlet: csp/crash.c
Client : 127.0.0.1
Query : /csp?crash
----------------------------------------