From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix gdb.threads/check-libthread-db.exp with glibc 2.34
Date: Thu, 7 Oct 2021 11:28:18 -0400 [thread overview]
Message-ID: <bee513fd-d948-8af5-fc2d-30cad710ca62@simark.ca> (raw)
In-Reply-To: <20211007125009.GA23264@delia.home>
On 2021-10-07 8:50 a.m., Tom de Vries via Gdb-patches wrote:
> Hi,
>
> When running test-case gdb.threads/check-libthread-db.exp on openSUSE
> Tumbleweed (with glibc 2.34) I get:
> ...
> (gdb) continue^M
> Continuing.^M
> [Thread debugging using libthread_db enabled]^M
> Using host libthread_db library "/lib64/libthread_db.so.1".^M
> Stopped due to shared library event:^M
> Inferior loaded /lib64/libm.so.6^M
> /lib64/libc.so.6^M
> (gdb) FAIL: gdb.threads/check-libthread-db.exp: user-initiated check: continue
> ...
>
> The check expect the inferior to load libpthread, but since glibc 2.34
> libpthread has been integrated into glibc, and consequently it's no longer
> a dependency:
> ...
> $ ldd outputs/gdb.threads/check-libthread-db/check-libthread-db
> linux-vdso.so.1 (0x00007ffe4cae4000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f167c77c000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f167c572000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f167c86e000)
> ...
>
> Fix this by updating the regexp to expect libpthread or libc.
>
> Tested on x86_64-linux.
>
> Any comments?
>
> Thanks,
> - Tom
>
> [gdb/testsuite] Fix gdb.threads/check-libthread-db.exp with glibc 2.34
>
> ---
> gdb/testsuite/gdb.threads/check-libthread-db.exp | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/gdb.threads/check-libthread-db.exp b/gdb/testsuite/gdb.threads/check-libthread-db.exp
> index 6ecf40db6a9..423c29978c8 100644
> --- a/gdb/testsuite/gdb.threads/check-libthread-db.exp
> +++ b/gdb/testsuite/gdb.threads/check-libthread-db.exp
> @@ -58,7 +58,9 @@ with_test_prefix "user-initiated check" {
>
> # User-initiated check with NPTL possibly uninitialized.
> gdb_test "continue" \
> - ".*Stopped due to shared library event.*Inferior loaded .*libpthread.*"
> + [multi_line \
> + "Stopped due to shared library event:" \
> + " Inferior loaded .*(libpthread|libc).*"]
>
> gdb_test_sequence "maint check libthread-db" \
> "libpthread.so possibly not initialized" \
>
LGTM, thanks.
Simon
prev parent reply other threads:[~2021-10-07 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 12:50 Tom de Vries via Gdb-patches
2021-10-07 15:28 ` Simon Marchi [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=bee513fd-d948-8af5-fc2d-30cad710ca62@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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