| Summary: | valgrind 3.15.0-RC1 fails gdbserver_tests because of gdb output change | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Roger Light <roger> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | mark |
| Priority: | NOR | ||
| Version First Reported In: | 3.15 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
commit 0c8be9bbede189ec580ec270521811766429595f Author: Mark Wielaard <mark@klomp.org> Date: Wed Apr 10 01:28:24 2019 +0200 gdbserver_tests fails because of gdb output change. The 'done.' in "Reading symbols from <exe>...done." is optional. https://bugs.kde.org/show_bug.cgi?id=406357 Reported-by: Roger Light <roger@atchoo.org> |
On Ubuntu 19.04 amd64 / gdb 8.2.90.20190311 the output format of gdb has changed from Reading symbols from <exe>...done. to Reading symbols from <exe>... This results in a raft of stdoutB errors in gdbserver_tests. This fixes it: diff --git a/gdbserver_tests/filter_gdb b/gdbserver_tests/filter_gdb index 05bbe4c54..d0ab11ddb 100755 --- a/gdbserver_tests/filter_gdb +++ b/gdbserver_tests/filter_gdb @@ -92,7 +92,7 @@ sed -e '/Remote debugging using/,/vgdb launched process attached/d' -e 's/^Thread .... received /Program received /' \ -e 's/#[0-9]\( 0x........ in sleeper_or_burner\)/#.\1/' \ -e 's/\(#0 0x........ in do_burn ()\) at sleepers.c:41/\1/' \ - -e '/^Reading symbols from .*\.\.\.done\./d' \ + -e '/^Reading symbols from .*\.\.\.\(done\.\)\?/d' \ -e '/^Loaded symbols for .*$/d' \ -e '/^Current language.*/d' \ -e '/^The current source language is.*/d' \