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/29919] [gdb/testsuite] FAIL: gdb.base/print-symbol-loading.exp: shlib off: load shared-lib
Date: Sat, 31 Dec 2022 06:36:02 +0000	[thread overview]
Message-ID: <bug-29919-4717-hP1ZVhf0TL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29919-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 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=38ef8cc8e80fe7dc33152af1f85e7530e66f51b8

commit 38ef8cc8e80fe7dc33152af1f85e7530e66f51b8
Author: Tom de Vries <tdevries@suse.de>
Date:   Sat Dec 31 07:35:56 2022 +0100

    [gdb/testsuite] Fix gdb.base/print-symbol-loading.exp on ubuntu 22.04.1

    On ubuntu 22.04.1 x86_64, I run into:
    ...
    (gdb) PASS: gdb.base/print-symbol-loading.exp: shlib off: \
      set print symbol-loading off
    sharedlibrary .*^M
    Symbols already loaded for /lib/x86_64-linux-gnu/libc.so.6^M
    Symbols already loaded for /lib/x86_64-linux-gnu/libpthread.so.0^M
    (gdb) FAIL: gdb.base/print-symbol-loading.exp: shlib off: load shared-lib
    ...

    The test-case expects the libc.so line, but not the libpthread.so line.

    However, we have:
    ...
    $ ldd /lib/x86_64-linux-gnu/libc.so.6
            linux-vdso.so.1 (0x00007ffd7f7e7000)
            libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0
(0x00007f4468c00000)
            /lib64/ld-linux-x86-64.so.2 (0x00007f4469193000)
            libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4468f3e000)
            libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f4468f39000)
    ...
    so it's not unexpected that libpthread.so is loaded if libc.so is loaded.

    Fix this by accepting the libpthread.so line.

    Tested on x86_64-linux.

    PR testsuite/29919
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29919

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

  reply	other threads:[~2022-12-31  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  8:49 [Bug testsuite/29919] New: " vries at gcc dot gnu.org
2022-12-31  6:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-31  6:38 ` [Bug testsuite/29919] " 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-29919-4717-hP1ZVhf0TL@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).