[llvm-commits] CVS: llvm-test/RunSafely.sh RunSafelyAndStable.sh

[Andrew Lenharth]

Changes in directory llvm-test:

RunSafely.sh updated: 1.17 -> 1.18
RunSafelyAndStable.sh updated: 1.3 -> 1.4
---
Log message:

So if gdb gets in a loop reading stack frames, disks fill up.  a backtrace of 100 frames should be enough for anybody

---
Diffs of the changes:  (+2 -2)

 RunSafely.sh          |    2 +-
 RunSafelyAndStable.sh |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


Index: llvm-test/RunSafely.sh
diff -u llvm-test/RunSafely.sh:1.17 llvm-test/RunSafely.sh:1.18
--- llvm-test/RunSafely.sh:1.17	Wed Dec 29 21:10:38 2004
+++ llvm-test/RunSafely.sh	Thu Jul 28 12:02:07 2005
@@ -67,7 +67,7 @@
     fi
 
     corefile=`ls core* | head -n 1`
-    echo "where" > StackTrace.$$
+    echo "where 100" > StackTrace.$$
     $GDB -q -batch --command=StackTrace.$$ --core=$corefile $PROGRAM < /dev/null
     rm -f StackTrace.$$ $corefile
 fi


Index: llvm-test/RunSafelyAndStable.sh
diff -u llvm-test/RunSafelyAndStable.sh:1.3 llvm-test/RunSafelyAndStable.sh:1.4
--- llvm-test/RunSafelyAndStable.sh:1.3	Wed Nov 10 13:49:27 2004
+++ llvm-test/RunSafelyAndStable.sh	Thu Jul 28 12:02:07 2005
@@ -63,7 +63,7 @@
     fi
 
     corefile=`ls core* | head -n 1`
-    echo "where" > StackTrace.$$
+    echo "where 100" > StackTrace.$$
     $GDB -q -batch --command=StackTrace.$$ --core=$corefile $PROGRAM < /dev/null
     rm -f StackTrace.$$ $corefile
     exit 0