13b290486cd4cd601b20e04340e593c9ed9717e5fsewardj#! /bin/sh 23b290486cd4cd601b20e04340e593c9ed9717e5fsewardj 33b290486cd4cd601b20e04340e593c9ed9717e5fsewardjdir=`dirname $0` 43b290486cd4cd601b20e04340e593c9ed9717e5fsewardj 53b290486cd4cd601b20e04340e593c9ed9717e5fsewardj$dir/filter_stderr | 63b290486cd4cd601b20e04340e593c9ed9717e5fsewardj 73b290486cd4cd601b20e04340e593c9ed9717e5fsewardj# Anonymise addresses 83b290486cd4cd601b20e04340e593c9ed9717e5fsewardj$dir/../tests/filter_addresses | 93b290486cd4cd601b20e04340e593c9ed9717e5fsewardj 10eefeeb7a60a347bc851605fadd52672cbd927201sewardj# filter vgdb process id, 11eefeeb7a60a347bc851605fadd52672cbd927201sewardj# pid 12eefeeb7a60a347bc851605fadd52672cbd927201sewardj# gdb 7.2 sometimes tries to access address 0x0 (same as with standard gdbserver) 13eefeeb7a60a347bc851605fadd52672cbd927201sewardj# filter a debian 6.0/ppc32 line 143b290486cd4cd601b20e04340e593c9ed9717e5fsewardjsed -e 's/\(relaying data between gdb and process \)[0-9][0-9]*/\1..../' \ 153b290486cd4cd601b20e04340e593c9ed9717e5fsewardj -e 's/\(sending command .* to pid \)[0-9][0-9]*/\1..../' \ 16eefeeb7a60a347bc851605fadd52672cbd927201sewardj -e '/Cannot access memory at address 0x......../d' \ 17900863d80e67d19eafbf214f62e46b97e8c5203cflorian -e '/^[1-9][0-9]* \.\.\/sysdeps\/powerpc\/powerpc32\/dl-start\.S: No such file or directory\./d' | 18900863d80e67d19eafbf214f62e46b97e8c5203cflorian 19900863d80e67d19eafbf214f62e46b97e8c5203cflorian# filter some debuginfo problems with ld.so and SLES11 20dcf6394a08fbfed3b30d2fb273b994aec87c3ce4mjwsed -e '/^1 rtld.c: No such file or directory\./d' | 21dcf6394a08fbfed3b30d2fb273b994aec87c3ce4mjw 22dcf6394a08fbfed3b30d2fb273b994aec87c3ce4mjw# and filter out any remaining empty lines 23dcf6394a08fbfed3b30d2fb273b994aec87c3ce4mjwsed -e '/^$/d' 24