From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Fix mi-exec-run.exp with native-extended-gdbserver
Date: Wed, 27 Apr 2022 19:17:25 +0100 [thread overview]
Message-ID: <cover.1651083290.git.aburgess@redhat.com> (raw)
While testing another patch I hit some unstable test failures in
mi-exec-run.exp, when using native-extended-gdbserver board.
These two patches fix the two separate issues that were impacting this
test.
Now I see no failures for mi-exec-run.exp using the unix board, or the
native-extended-gdbserver board.
---
Andrew Burgess (2):
gdb: fix failures in gdb.mi/mi-exec-run.exp with
native-extended-gdbserver
gdb/testsuite: fix native-extended-gdbserver failure in
mi-exec-run.exp
.../boards/native-extended-gdbserver.exp | 2 +-
gdb/testsuite/gdb.mi/mi-break-qualified.exp | 2 +-
gdb/testsuite/gdb.mi/mi-exec-run.exp | 91 ++++++++++++++-----
gdb/testsuite/lib/mi-support.exp | 24 +++--
4 files changed, 86 insertions(+), 33 deletions(-)
--
2.25.4
next reply other threads:[~2022-04-27 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 18:17 Andrew Burgess [this message]
2022-04-27 18:17 ` [PATCH 1/2] gdb: fix failures in gdb.mi/mi-exec-run.exp " Andrew Burgess
2022-04-27 18:42 ` Pedro Alves
2022-04-27 18:17 ` [PATCH 2/2] gdb/testsuite: fix native-extended-gdbserver failure in mi-exec-run.exp Andrew Burgess
2022-04-28 11:27 ` [PATCHv2 0/2] Fix mi-exec-run.exp with native-extended-gdbserver Andrew Burgess
2022-04-28 11:27 ` [PATCHv2 1/2] gdb: fix failures in gdb.mi/mi-exec-run.exp " Andrew Burgess
2022-04-29 13:52 ` Pedro Alves
2022-04-28 11:27 ` [PATCHv2 2/2] gdb/testsuite: fix native-extended-gdbserver failure in mi-exec-run.exp Andrew Burgess
2022-04-29 14:13 ` Pedro Alves
2022-04-29 18:15 ` [PATCHv3 0/3] gdb/testsuite: fix mi-exec-run.exp Andrew Burgess
2022-04-29 18:15 ` [PATCHv3 1/3] gdb/testsuite: fix mi-exec-run.exp with native-extended-gdbserver board Andrew Burgess
2022-04-29 18:15 ` [PATCHv3 2/3] gdb/testsuite: change mi_gdb_start to take a list of flags Andrew Burgess
2022-04-29 18:15 ` [PATCHv3 3/3] gdb/testsuite: small cleanup in mi-break-qualified.exp Andrew Burgess
2022-05-02 16:37 ` [PATCHv3 0/3] gdb/testsuite: fix mi-exec-run.exp Pedro Alves
2022-05-03 9:49 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1651083290.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).