From 985c7da604ac30e67ee4b5a829935074900d6f26 Mon Sep 17 00:00:00 2001
From: Andrew Bartlett <abartlet@samba.org>
Date: Tue, 22 Feb 2011 12:28:33 +1100
Subject: selftest: Improve gdb_backtrace to run in batch mode

Following Tridge's advice, we need to have no input (/dev/null) and
-batch for reliable opeation on big backtraces.

We should also use --pid, and let gdb find the binary

Andrew Bartlett
---
 selftest/gdb_backtrace | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'selftest/gdb_backtrace')

diff --git a/selftest/gdb_backtrace b/selftest/gdb_backtrace
index 91637ec40c..5531814149 100755
--- a/selftest/gdb_backtrace
+++ b/selftest/gdb_backtrace
@@ -102,12 +102,13 @@ EOF
 	;;
 	gdb)
 cat << EOF  > ${BATCHFILE_MAIN}
-set height 1000
+set height 0
 bt full
+thread apply all bt full
 info locals
 quit
 EOF
-	${DB_BIN} -x "${BATCHFILE_MAIN}" "${BINARY}" "${PID}"
+	${DB_BIN} -batch -x "${BATCHFILE_MAIN}" --pid "${PID}" < /dev/null
 	;;
 dbx)
 	${DB_BIN} "where;dump;kill;quit" "${BINARY}" "${PID}"
-- 
cgit