public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/17016] XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete
Date: Fri, 30 Dec 2022 15:53:55 +0000	[thread overview]
Message-ID: <bug-17016-4717-nRaiPVpE4b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17016-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17016

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cb2a1d0aca416235aed885e4796eeb70fbcd3b95

commit cb2a1d0aca416235aed885e4796eeb70fbcd3b95
Author: Tom de Vries <tdevries@suse.de>
Date:   Fri Dec 30 16:53:51 2022 +0100

    [gdb/testsuite] Fix gdb.threads/dlopen-libpthread.exp for upstream glibc

    On ubuntu 22.04.1 x86_64, I run into:
    ...
    (gdb) info probes all rtld rtld_map_complete^M
    No probes matched.^M
    (gdb) XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld
rtld_map_complete
    UNTESTED: gdb.threads/dlopen-libpthread.exp: no matching probes
    ...
    This has been filed as PR testsuite/17016.

    The problem is that the name rtld_map_complete is used, which was only
    available in Fedora 17, and upstream the name map_complete was used.

    In the email thread discussing a proposed patch (
    https://sourceware.org/legacy-ml/gdb-patches/2014-09/msg00712.html ) it was
    suggested to make the test-case handle both names.

    So, handle both names: map_complete and rtld_map_complete.

    This exposes the following FAIL:
    ...
    (gdb) info sharedlibrary^M
    From To    Syms Read Shared Object Library^M
    $hex $hex  Yes       /lib64/ld-linux-x86-64.so.2^M
    $hex $hex  Yes (*)   /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0^M
    $hex $hex  Yes       /lib/x86_64-linux-gnu/libc.so.6^M
    $hex $hex  Yes       /lib/x86_64-linux-gnu/libdl.so.2^M
    $hex $hex  Yes       /lib/x86_64-linux-gnu/libpthread.so.0^M
    (*): Shared library is missing debugging information.^M
    (gdb) FAIL: gdb.threads/dlopen-libpthread.exp: libpthread.so not found
    ...
    due to using a glibc (v2.35) that has libpthread integrated into libc.

    Fix this by changing the FAIL into UNSUPPORTED.

    Tested on x86_64-linux.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=17016

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-12-30 15:53 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
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 [this message]
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-nRaiPVpE4b@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).