From: Lirong Yuan <yuanzi@google.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] [PATCH v2] gdbstub: add support to Xfer:auxv:read: packet
Date: Mon, 3 Aug 2020 10:05:58 -0700 [thread overview]
Message-ID: <CADjx4CJOGbYa_8W7f1KDF8qwTJhVwV75SA1G3TGHv+Mz3cXvFg@mail.gmail.com> (raw)
In-Reply-To: <87bljsnf5p.fsf@linaro.org>
On Mon, Aug 3, 2020 at 4:27 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Lirong Yuan <yuanzi@google.com> writes:
>
> > This allows gdb to access the target’s auxiliary vector,
> > which can be helpful for telling system libraries important details
> > about the hardware, operating system, and process.
> >
> > Signed-off-by: Lirong Yuan <yuanzi@google.com>
>
> I cleaned up the test a little:
>
> modified tests/tcg/multiarch/gdbstub/test-qxfer-auxv-read.py
> @@ -22,13 +22,9 @@ def report(cond, msg):
> def run_test():
> "Run through the tests one by one"
>
> - cond = True
> - try:
> - gdb.execute("info auxv")
> - except (gdb.error, AttributeError):
> - cond = False
> -
> - report(cond, "Display the auxiliary vector of the inferior.")
> + auxv = gdb.execute("info auxv", False, True)
> + report(isinstance(auxv, str), "Fetched auxv from inferior")
> + report(auxv.find("sha1"), "Found test binary name in auxv")
>
> #
> # This runs as the script it sourced (via -x, via run-test.py)
>
>
> Queued to gdbstub/next, thanks.
>
> --
> Alex Bennée
Awesome, thank you Alex for the review and cleanup!
Regards,
Lirong
prev parent reply other threads:[~2020-08-03 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 19:39 [PATCH] [PATCH v2] gdbstub: add support to Xfer:auxv:read: packet Lirong Yuan
2020-08-03 11:26 ` Alex Bennée
2020-08-03 17:05 ` Lirong Yuan [this message]
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=CADjx4CJOGbYa_8W7f1KDF8qwTJhVwV75SA1G3TGHv+Mz3cXvFg@mail.gmail.com \
--to=yuanzi@google.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).