public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/27744] Support different libpthread/ld.so load orders in libthread_db
Date: Wed, 21 Apr 2021 11:45:22 +0000	[thread overview]
Message-ID: <bug-27744-131-otwHGEqV4M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27744-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a64afc225240b2b27129ccfb0516d7c958b98040

commit a64afc225240b2b27129ccfb0516d7c958b98040
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Apr 21 11:50:43 2021 +0200

    nptl_db: Support different libpthread/ld.so load orders (bug 27744)

    libthread_db is loaded once GDB encounters libpthread, and at this
    point, ld.so may not have been processed by GDB yet. As a result,
    _rtld_global cannot be accessed by regular means from libthread_db.
    To make this work until GDB can be fixed, acess _rtld_global through
    a pointer stored in libpthread.

    The new test does not reproduce bug 27744 with
    --disable-hardcoded-path-in-tests, but is still a valid smoke test.
    With --enable-hardcoded-path-in-tests, it is necessary to avoid
    add-symbol-file because this can tickle a GDB bug.

    Fixes commit 1daccf403b1bd86370eb94edca794dc106d02039 ("nptl: Move
    stack list variables into _rtld_global").

    Tested-by: Emil Velikov <emil.velikov@collabora.com>

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

  parent reply	other threads:[~2021-04-21 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 15:20 [Bug nptl/27744] New: " fweimer at redhat dot com
2021-04-16 15:25 ` [Bug nptl/27744] " fweimer at redhat dot com
2021-04-16 15:58 ` fweimer at redhat dot com
2021-04-21 11:45 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-21 11:46 ` fweimer at redhat dot com
2021-04-26  6:25 ` fweimer at redhat dot com
2021-04-30  7:19 ` cvs-commit at gcc dot gnu.org
2021-05-06 13:05 ` 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-27744-131-otwHGEqV4M@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).