Too difficult to match the stacktrace of the last instruction
of a program => let's remove these (uninteresting) lines
rather than trying to 'sed' them to make them look the same
on different OS/platform/....
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13906 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/gdbserver_tests/filter_gdb b/gdbserver_tests/filter_gdb
index a31cb0f..71463ab 100755
--- a/gdbserver_tests/filter_gdb
+++ b/gdbserver_tests/filter_gdb
@@ -20,6 +20,8 @@
# output of the echo command telling it is launched.
# This removes a whole lot of uninteresting lines varying
# with OS/glibc/gdb dep
+# then have a general way to delete uninteresting and vayring
+# lines.
# initial tty control character sent by gdb 7.0
# remove missing debuginfos
# vgdb message
@@ -54,6 +56,7 @@
# 'exited with code' and 'exited normally' are printed slightly
# differently between gdb versions, normalize to "Program exited...".
sed -e '/Remote debugging using/,/vgdb launched process attached/d' \
+ -e '/filter_gdb BEGIN drop/,/filter_gdb END drop/d' \
-e 's/^\[?1034hReading symbols/Reading symbols/' \
-e '/^Missing separate debuginfo/d' \
-e '/^Try: zypper install -C/d' \
diff --git a/gdbserver_tests/nlgone_exit.stdinB.gdb b/gdbserver_tests/nlgone_exit.stdinB.gdb
index 3724be6..2ed6ed3 100644
--- a/gdbserver_tests/nlgone_exit.stdinB.gdb
+++ b/gdbserver_tests/nlgone_exit.stdinB.gdb
@@ -2,7 +2,9 @@
target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlgone-exit
echo vgdb launched process attached\n
# continue after startup
+echo filter_gdb BEGIN drop\n
continue
+echo filter_gdb END drop\n
# continue at the last instruction
continue
# see program is gone with exit code
diff --git a/gdbserver_tests/nlgone_exit.stdoutB.exp b/gdbserver_tests/nlgone_exit.stdoutB.exp
index 3f4c712..081e862 100644
--- a/gdbserver_tests/nlgone_exit.stdoutB.exp
+++ b/gdbserver_tests/nlgone_exit.stdoutB.exp
@@ -1,5 +1,2 @@
Continuing.
-Program received signal SIGTRAP, Trace/breakpoint trap.
-0x........ in syscall ...
-Continuing.
Program exited with code 01.