From feb6b52f0f83ac1f6f2a35537e6e541f9d3a3110 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Tue, 3 Apr 2018 16:58:18 +0930 Subject: [PATCH] lightningd: don't try to perform backtrace if LIGHTNINGD_DEV_NO_BACKTRACE Valgrind gets upset. Signed-off-by: Rusty Russell --- common/daemon.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/common/daemon.c b/common/daemon.c index 14d8d4a31..5ecc4ba41 100644 --- a/common/daemon.c +++ b/common/daemon.c @@ -33,11 +33,13 @@ static void crashdump(int sig) { /* We do stderr first, since it's most reliable. */ warnx("Fatal signal %d", sig); - backtrace_print(backtrace_state, 0, stderr); + if (backtrace_state) + backtrace_print(backtrace_state, 0, stderr); /* Now send to parent. */ bt_print("FATAL SIGNAL %d", sig); - backtrace_full(backtrace_state, 0, backtrace_status, NULL, NULL); + if (backtrace_state) + backtrace_full(backtrace_state, 0, backtrace_status, NULL, NULL); /* Probably shouldn't return. */ bt_exit();