How it works...
In the first step, we triggered a segmentation fault in the Redis instance using the command DBBUG SEGFAULT. The instance crashed immediately. It can be seen clearly from the running log of the Redis instance that the process has crashed and all the information, including the stack trace, the output of the INFO command, the clients' information, and the registers have been logged in the log file. If the crash can be reproduced, we could use GDB to attach to the Redis process for further debugging. Take note; you always perform debugging in your testing environment. After the GDB is attached to the redis-server process, just use the command c to let the Redis process continue running. For demonstration purposes, we crashed ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access