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/31293] gdb.threads/threadcrash.exp failure
Date: Mon, 11 Mar 2024 09:57:15 +0000	[thread overview]
Message-ID: <bug-31293-4717-arXkRoRPyc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31293-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Sourceware Commits <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=f215d2d8ad7bc1f80e68a962196f0e6dc02951c9

commit f215d2d8ad7bc1f80e68a962196f0e6dc02951c9
Author: Guinevere Larsen <blarsen@redhat.com>
Date:   Mon Mar 11 10:57:32 2024 +0100

    gdb/testsuite: Reduce gdb.threads/threadcrash.exp reliance on libc symbols

    The test gdb.threads/threadcrash.exp demanded GDB to fully unwind and
    print the names of all functions. However, some of the functions are
    from the libc library, and so the test implicitly demanded libc symbols
    to be available, and would fail otherwise, as was raised in PR
    gdb/31293.

    This commit changes it so we only explicitly check for functions that
    are not provided by threadcrash.c if they are indeed available.

    Tested on arm-linux and x86_64-linux.

    Approved-By: Tom de Vries <tdevries@suse.de>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31293

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

  parent reply	other threads:[~2024-03-11  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 12:44 [Bug gdb/31293] New: " simon.marchi at polymtl dot ca
2024-01-25 12:44 ` [Bug gdb/31293] " simon.marchi at polymtl dot ca
2024-01-25 12:57 ` blarsen at redhat dot com
2024-03-05  7:30 ` [Bug testsuite/31293] " vries at gcc dot gnu.org
2024-03-11  9:57 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-11  9:59 ` 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-31293-4717-arXkRoRPyc@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).