From: antirez <antirez@gmail.com>
Date: Sun, 18 Mar 2012 10:35:35 +0000 (+0100)
Subject: On crash suggest to give --test-memory a try.
X-Git-Url: https://git.saurik.com/redis.git/commitdiff_plain/d4e6ce3e97a4bb2ea9c25af2ad48e5ed9d0c5024?hp=-c

On crash suggest to give --test-memory a try.
---

d4e6ce3e97a4bb2ea9c25af2ad48e5ed9d0c5024
diff --git a/src/debug.c b/src/debug.c
index a355df05..8eea3bf8 100644
--- a/src/debug.c
+++ b/src/debug.c
@@ -636,8 +636,9 @@ void sigsegvHandler(int sig, siginfo_t *info, void *secret) {
 
     redisLog(REDIS_WARNING,
 "\n=== REDIS BUG REPORT END. Make sure to include from START to END. ===\n\n"
-"    Please report the crash opening an issue on github:\n\n"
-"        http://github.com/antirez/redis/issues\n\n"
+"       Please report the crash opening an issue on github:\n\n"
+"           http://github.com/antirez/redis/issues\n\n"
+"  Suspect RAM error? Use redis-server --test-memory to veryfy it.\n\n"
 );
     /* free(messages); Don't call free() with possibly corrupted memory. */
     if (server.daemonize) unlink(server.pidfile);