Closed ghost closed 11 years ago
The async hiredis client calls its onConnect
function pointer when a connection is made, if it is non-NULL.
Maybe this function pointer is set to garbage in your case, resulting in the segmentation fault.
Can you inspect your core to check if this is the case or not? If it is non-NULL -- but not garbage -- the segmentation fault may be caused by code in your callback.
Hi , Here is the stack trace of the application which uses redis async api for performing queries . It's mostly random but happens when redis-server is killed .we are using libev for polling mechanism