Commit 31b7e977 authored by fogal1's avatar fogal1

Made gdb at least print out a backtrace.

When not using an xterm for debugging, the gdb we run is not
interactive.  This makes it difficult to figure out where,
exactly, a component crashed.  This adds a backtrace print to our
gdb input file, to make sure we always get at least some useful

Also gdb's startup banner is spammy; -q[uiet] it.

git-svn-id: 18c085ea-50e0-402c-830e-de6fd14e8384
parent b1891e96
......@@ -498,6 +498,9 @@ $0 = shift @ARGV;
# on the command line. This allows '--help' to be passed to visit cli
# scripts which may have their own help and argument processing.
# Tom Fogal, Sun Jun 28 22:18:04 MDT 2009
# Made gdb at least print out a backtrace.
# Mark C. Miller, Tue Jul 7 18:00:34 PDT 2009
# Added logic to avoid backtick pwd if possible. That is causing problems
# on LLNL systems when ANY lscratch filesystem happens to be down and
......@@ -2837,10 +2840,14 @@ else
# If the user did not break in main, continue.
if($breakmain eq 0) { print GDBFILE "continue\n"; }
print GDBFILE "bt full\n";
close GDBFILE;
# Run gdb directly
@debugcmd = ("gdb", $real_exe, "-x", $gdbfilename);
@debugcmd = ("gdb", "-q", $real_exe, "-x", $gdbfilename);
# Run GDB under an xterm
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment