From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] gdb/testsuite: Add test that reads auxv in a multi-threaded inferior
Date: Tue, 4 Apr 2023 16:00:50 +0200 [thread overview]
Message-ID: <CAJVr-EO87gb+uQrbrvEA+kLKC0EJfJhvEgkKSpYoM4H1XLnVkg@mail.gmail.com> (raw)
In-Reply-To: <20230331034432.3037148-6-thiago.bauermann@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
On Fri, Mar 31, 2023 at 5:46 AM Thiago Jung Bauermann via Gdb-patches <
gdb-patches@sourceware.org> wrote:
> This test exercises reading the auxiliary vector in a program where the
> main thread exits before other threads.
>
> Because GDB's auxv cache makes it difficult to hit the race that this test
> exercises, add a maintenance command that flushes the cache.
>
> Also, move the fetch_auxv procedure from gdb.base/auxv to lib/gdb.exp so
> that the new testcase can use it.
> ---
> gdb/auxv.c | 16 ++++++++
> gdb/testsuite/gdb.base/auxv.exp | 56 ---------------------------
> gdb/testsuite/gdb.threads/auxv.c | 62 ++++++++++++++++++++++++++++++
> gdb/testsuite/gdb.threads/auxv.exp | 30 +++++++++++++++
> gdb/testsuite/lib/gdb.exp | 62 ++++++++++++++++++++++++++++++
> 5 files changed, 170 insertions(+), 56 deletions(-)
> create mode 100644 gdb/testsuite/gdb.threads/auxv.c
> create mode 100644 gdb/testsuite/gdb.threads/auxv.exp
>
>
I tested the series on ppc64le and I've got a failure for
gdb.threads/auxv.exp:
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using
/root/build_upstream/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/config/unix.exp
as tool-and-target-specific interface file.
Running
/root/build_upstream/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.threads/auxv.exp
...
WARNING: Unrecognized tag value: 27 ???
0x1c
WARNING: Unrecognized tag value: 28 ???
0x20
FAIL: gdb.threads/auxv.exp: Get auxv after main thread exits
=== gdb Summary ===
# of expected passes 1
# of unexpected failures 1
Regards,
Alexandra
next prev parent reply other threads:[~2023-04-04 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 3:44 [PATCH 0/5] gdbserver: Follow-up on linux_get_auxv using PID parameter Thiago Jung Bauermann
2023-03-31 3:44 ` [PATCH 1/5] gdbserver: Use current_process in handle_qxfer_auxv Thiago Jung Bauermann
2023-03-31 3:44 ` [PATCH 2/5] gdbserver: Use the PID of the current process instead of the current thread Thiago Jung Bauermann
2023-03-31 3:44 ` [PATCH 3/5] gdbserver/linux: Read auxv from any thread of the process Thiago Jung Bauermann
2023-03-31 3:44 ` [PATCH 4/5] gdb/linux-nat: " Thiago Jung Bauermann
2023-03-31 3:44 ` [PATCH 5/5] gdb/testsuite: Add test that reads auxv in a multi-threaded inferior Thiago Jung Bauermann
2023-04-04 14:00 ` Alexandra Petlanova Hajkova [this message]
2023-04-04 15:19 ` [PATCH 0/5] gdbserver: Follow-up on linux_get_auxv using PID parameter Simon Marchi
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=CAJVr-EO87gb+uQrbrvEA+kLKC0EJfJhvEgkKSpYoM4H1XLnVkg@mail.gmail.com \
--to=ahajkova@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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).