Replies: 1 comment
-
The reason why the StackTrace in the Redis sigsegvHandler() function is directed to stdout or a logfile instead of invoking serverLog() is to ensure that the traceback information is captured even in cases where the server is unable to log to its normal log file (e.g., if the SIGSEGV was caused by a disk failure or other system issue). By writing the traceback information directly to stdout or a separate logfile, the information can be captured even if the server is experiencing issues writing to its normal log file. Additionally, the use of stdout or a separate logfile allows for easier debugging and troubleshooting of the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Redis dumps information including traceback in sigsegvHandler() function while receiving signal like SIGABRT, SIGSEGV etc. My question is why the StackTrace in logStackTrace() function is direct to stdout or logfile but not invoking serverLog()? Any thoughts behind it?
Beta Was this translation helpful? Give feedback.
All reactions