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 exp/30271] Addresses of static thread_local fields are badly calculated sometimes
Date: Mon, 15 May 2023 14:51:48 +0000	[thread overview]
Message-ID: <bug-30271-4717-ofXPNRKiXc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30271-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

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

commit b10f2cd3f3c3b25c71e50a342fb46f9eb9eba792
Author: Tom Tromey <tom@tromey.com>
Date:   Fri Apr 28 13:04:15 2023 -0600

    Correctly handle forward DIE references in scanner

    The cooked index scanner has special code to handle forward DIE
    references.  However, a bug report lead to the discovery that this
    code does not work -- the "deferred_entry::spec_offset" field is
    written to but never used, i.e., the lookup is done using the wrong
    key.

    This patch fixes the bug and adds a regression test.

    The test in the bug itself used a thread_local variable, which
    provoked a failure at runtime.  This test instead uses "maint print
    objfiles" and then inspects to ensure that the entry in question has a
    parent.  This lets us avoid a clang dependency in the test.

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

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

  parent reply	other threads:[~2023-05-15 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 18:44 [Bug exp/30271] New: " michal.chojnowski at scylladb dot com
2023-03-25 16:37 ` [Bug exp/30271] " tromey at sourceware dot org
2023-03-25 16:38 ` tromey at sourceware dot org
2023-03-25 20:28 ` tromey at sourceware dot org
2023-03-26  0:56 ` michal.chojnowski at scylladb dot com
2023-03-26  1:21 ` michal.chojnowski at scylladb dot com
2023-03-31 17:04 ` tromey at sourceware dot org
2023-03-31 17:12 ` tromey at sourceware dot org
2023-03-31 17:54 ` tromey at sourceware dot org
2023-03-31 18:00 ` tromey at sourceware dot org
2023-03-31 18:03 ` tromey at sourceware dot org
2023-05-10 23:28 ` tromey at sourceware dot org
2023-05-15 14:51 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-15 15:06 ` michal.chojnowski at scylladb dot com
2023-05-15 15:16 ` cvs-commit at gcc dot gnu.org
2023-05-15 15:17 ` tromey at sourceware dot 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-30271-4717-ofXPNRKiXc@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).