public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, gdb-patches@sourceware.org,
	 Simon Marchi <simon.marchi@polymtl.ca>,
	Kevin Buettner <kevinb@redhat.com>,
	 Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v2] nptl_db: Support different libpthread/ld.so load orders (bug 27744)
Date: Mon, 19 Apr 2021 11:50:32 +0100	[thread overview]
Message-ID: <CACvgo53dShRmc34ZZWDahBUCnUx-2Gs=51jYVECzEPRv+X8n7A@mail.gmail.com> (raw)
In-Reply-To: <87czuum5yb.fsf@oldenburg.str.redhat.com>

Hi Florian,

On Fri, 16 Apr 2021 at 19:37, Florian Weimer <fweimer@redhat.com> wrote:
>
> 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").
>
> ---
> v2: Fixes suggested by Pedro.  The static tests is now actually built
>     and run.
>
Thanks for the prompt fix. Both v1 and v2 fix the issue for me with
gimp and steam.

Feel free to add:
Tested-by: Emil Velikov <emil.velikov@collabora.com>

Are there any plans for glibc 2.33.1 or shall I ask the Arch Linux
maintainers to include this in the package?

Thanks again,
Emil

  reply	other threads:[~2021-04-19 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 18:37 Florian Weimer
2021-04-19 10:50 ` Emil Velikov [this message]
2021-04-19 10:57   ` Florian Weimer
2021-04-27 11:46     ` Emil Velikov
2021-04-27 12:11       ` Florian Weimer
2021-04-30  7:20         ` Florian Weimer
2021-05-04 11:48           ` Emil Velikov

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='CACvgo53dShRmc34ZZWDahBUCnUx-2Gs=51jYVECzEPRv+X8n7A@mail.gmail.com' \
    --to=emil.l.velikov@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@polymtl.ca \
    /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).