13b290486cd4cd601b20e04340e593c9ed9717e5fsewardj#! /bin/sh
23b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
3d142f99836471d4245250247cc9ac7bc5a1391fasewardj# used to filter memcheck output shown by gdb/vgdb.
43b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
53b290486cd4cd601b20e04340e593c9ed9717e5fsewardjdir=`dirname $0`
63b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
73dfe979d03de6815008ecd66f9b733c7a44f0d2aflorian$dir/../memcheck/tests/filter_stderr "$@"              |
83b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
93b290486cd4cd601b20e04340e593c9ed9717e5fsewardj# filter vgdb messages
103b290486cd4cd601b20e04340e593c9ed9717e5fsewardj$dir/filter_vgdb                                       |
113b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
123b290486cd4cd601b20e04340e593c9ed9717e5fsewardj
13d142f99836471d4245250247cc9ac7bc5a1391fasewardj
14d142f99836471d4245250247cc9ac7bc5a1391fasewardj# filter some normal error messages provided by some gdb
15d142f99836471d4245250247cc9ac7bc5a1391fasewardj#
16d142f99836471d4245250247cc9ac7bc5a1391fasewardj# gdb 7.2 sometimes tries to access address 0x0 (same as with standard gdbserver)
17d142f99836471d4245250247cc9ac7bc5a1391fasewardj#
18d142f99836471d4245250247cc9ac7bc5a1391fasewardj# filter a debian 6.0/ppc32 line
19d142f99836471d4245250247cc9ac7bc5a1391fasewardj#
20d142f99836471d4245250247cc9ac7bc5a1391fasewardj# filter some missing info msg from s390
21d142f99836471d4245250247cc9ac7bc5a1391fasewardj#
223b290486cd4cd601b20e04340e593c9ed9717e5fsewardj# Bypass a s390x kernel bug which makes faultstatus test3 fail. In our case, we are
233b290486cd4cd601b20e04340e593c9ed9717e5fsewardj# not interested in checking the si_code, but rather the signal passing
243b290486cd4cd601b20e04340e593c9ed9717e5fsewardj# in mcsig(no)pass
25d142f99836471d4245250247cc9ac7bc5a1391fasewardjsed -e '/Cannot access memory at address 0x......../d'                   \
26d142f99836471d4245250247cc9ac7bc5a1391fasewardj    -e '/^[1-9][0-9]*	\.\.\/sysdeps\/powerpc\/powerpc32\/dl-start\.S: No such file or directory\./d' \
27d142f99836471d4245250247cc9ac7bc5a1391fasewardj    -e '/^Missing separate debuginfo/d'                                  \
28d142f99836471d4245250247cc9ac7bc5a1391fasewardj    -e '/^Try: zypper install -C/d'                                      \
29d142f99836471d4245250247cc9ac7bc5a1391fasewardj    -e 's/Test 3:   FAIL: expected si_code==2, not 128/Test 3:   PASS/'
30