public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17016] XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete
Date: Sat, 24 Dec 2022 07:45:03 +0000 [thread overview]
Message-ID: <bug-17016-4717-IcTDZqVN7b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17016-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17016
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
I did a test run on ubuntu 22.04.1 x86_64 and I'm also seeing this.
Reading through the thread pointed at by comment 1, it seems we need to test
both scenarios of Fedora 17 glibc and upstream glibc, but currently we only
test the former.
FWIW, I've tried removing the rtld_ prefix of rtld_map_complete in the
test-case, and ran into:
...
FAIL: libpthread.so not found
...
This is with glibc 2.35, which has libpthread integrated into glibc, so it's
not suprising that libpthread is already loaded at main.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-24 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 12:45 [Bug gdb/17016] New: " palves at redhat dot com
2014-09-24 18:04 ` [Bug gdb/17016] " sergiodj at redhat dot com
2014-09-24 18:04 ` sergiodj at redhat dot com
2022-12-24 7:45 ` vries at gcc dot gnu.org [this message]
2022-12-24 11:19 ` [Bug testsuite/17016] " vries at gcc dot gnu.org
2022-12-24 11:32 ` vries at gcc dot gnu.org
2022-12-30 15:53 ` cvs-commit at gcc dot gnu.org
2022-12-30 15:55 ` vries at gcc dot gnu.org
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=bug-17016-4717-IcTDZqVN7b@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).