From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3 2/2] gdb: Update test pattern to deal with native-extended-gdbserver
Date: Wed, 12 Dec 2018 16:13:00 -0000 [thread overview]
Message-ID: <f229a212-2496-0f3a-33a0-04713b54ccfa@redhat.com> (raw)
In-Reply-To: <4cef7f98656d92e8d4961840eff57b3810e4fc5d.1544625324.git.andrew.burgess@embecosm.com>
On 12/12/2018 03:16 PM, Andrew Burgess wrote:
> When running the test gdb.base/annota1.exp with:
>
> make check-gdb RUNTESTFLAGS="--target_board=native-extended-gdbserver gdb.base/annota1.exp"
>
> I would see a failure due to some unexpecte lines in GDB's output.
Typo: "unexpected"
LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-12-12 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 18:17 [PATCH] gdb/regcache: When saving, ignore registers that can't be read Andrew Burgess
2018-11-26 2:48 ` Simon Marchi
2018-11-27 11:13 ` [PATCHv2 2/3] " Andrew Burgess
2018-11-27 12:41 ` Pedro Alves
2018-11-27 15:30 ` Andrew Burgess
2018-11-27 16:57 ` Pedro Alves
2018-11-27 11:13 ` [PATCHv2 3/3] gdb: Update test pattern to deal with native-extended-gdbserver Andrew Burgess
2018-11-27 11:13 ` [PATCHv2 0/3] Handle Errors While Preparing For Inferior Call Andrew Burgess
2018-12-12 15:16 ` [PATCHv3 1/2] gdb/infcall: Make infcall_suspend_state more class like Andrew Burgess
2018-12-12 16:13 ` Pedro Alves
2018-12-12 15:16 ` [PATCHv3 0/2] Handle Errors While Preparing For Inferior Call Andrew Burgess
2018-12-12 16:14 ` Pedro Alves
2018-12-12 17:40 ` Andrew Burgess
2018-12-12 15:16 ` [PATCHv3 2/2] gdb: Update test pattern to deal with native-extended-gdbserver Andrew Burgess
2018-12-12 16:13 ` Pedro Alves [this message]
2018-11-27 11:13 ` [PATCHv2 1/3] gdb/infcall: Make infcall_suspend_state more class like 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=f229a212-2496-0f3a-33a0-04713b54ccfa@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.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