From 835b293d35a209d38047126443d41fa7090daa4c Mon Sep 17 00:00:00 2001
From: Justus Winter <justus@gnupg.org>
Date: Mon, 19 Jun 2017 21:20:57 +0200
Subject: Use our own variant of 'assert' and 'assert_perror'.

Our variants print stack traces on failures.  This will make locating
errors much easier.
---
 utils/login.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'utils/login.c')

diff --git a/utils/login.c b/utils/login.c
index 9ee296aa..1a12c3cd 100644
--- a/utils/login.c
+++ b/utils/login.c
@@ -30,7 +30,7 @@
 #include <grp.h>
 #include <netdb.h>
 #include <time.h>
-#include <assert.h>
+#include <assert-backtrace.h>
 #include <version.h>
 #include <sys/mman.h>
 
@@ -314,7 +314,7 @@ check_login (process_t proc_server, int lid)
   if (err == ESRCH)
     exit (42);			/* Nothing left to watch. */
   else
-    assert_perror (err);
+    assert_perror_backtrace (err);
 
   if (owned)
     exit (0);			/* Our task is done.  */
@@ -648,7 +648,7 @@ main(int argc, char *argv[])
   }
 
   err = proc_getsid (proc_server, pid, &sid);
-  assert_perror (err);		/* This should never fail.  */
+  assert_perror_backtrace (err);		/* This should never fail.  */
 
   if (!no_login
       && (parent_uids.num != 0
-- 
cgit v1.2.3