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
This commit is contained in:
Philippe Waroquiers 2014-04-24 21:52:02 +00:00
parent e548d704c3
commit ac230f7fcb
3 changed files with 5 additions and 3 deletions

View File

@ -20,6 +20,8 @@ sed -e '/^\ \ \ \ \.\.\.$/d' |
# 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 @@ sed -e '/^\ \ \ \ \.\.\.$/d' |
# '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' \

View File

@ -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

View File

@ -1,5 +1,2 @@
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x........ in syscall ...
Continuing.
Program exited with code 01.