diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2023-04-28 14:39:03 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2023-04-28 16:48:21 +0100 |
| commit | 1f7f972f59470104734ec705c985ab319eb580db (patch) | |
| tree | 07bb2abd05dbd499a8fccdbe2edfece6f07b7d23 /gdb/testsuite/gdb.server/reconnect-ctrl-c.c | |
| parent | 64b59b6bb2261fe2fa8310f94b4ed420c162e357 (diff) | |
| download | gdb-1f7f972f59470104734ec705c985ab319eb580db.zip gdb-1f7f972f59470104734ec705c985ab319eb580db.tar.gz gdb-1f7f972f59470104734ec705c985ab319eb580db.tar.bz2 | |
gdb/testsuite: additional test fixes after gdb_test changes
After this commit:
commit e2f620135d92f7cd670af4e524fffec7ac307666
Date: Thu Mar 30 13:26:25 2023 +0100
gdb/testsuite: change newline patterns used in gdb_test
There were some regressions in gdb.trace/*.exp tests when run with the
native-gdbserver board. This commit fixes these regressions.
All the problems are caused by unnecessary trailing newline characters
included in the patterns passed to gdb_test. After the above commit
the testsuite is stricter when matching trailing newlines, and so the
additional trailing newline characters are now causing the test to
fail. Fix by removing all the excess trailing newline characters.
In some cases this cleanup means we should use gdb_test_no_output,
I've done that where appropriate. In a couple of other places I've
made use of multi_line to better build the expected output pattern.
Diffstat (limited to 'gdb/testsuite/gdb.server/reconnect-ctrl-c.c')
0 files changed, 0 insertions, 0 deletions