public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: gdb-patches@sourceware.org,  Pedro Alves <palves@redhat.com>,
	 Kevin Buettner <kevinb@redhat.com>,
	 Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v3] nptl_db: Support different libpthread/ld.so load orders (bug 27744)
Date: Wed, 21 Apr 2021 13:47:01 +0200	[thread overview]
Message-ID: <87czunoo5m.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87tuo24kxi.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 19 Apr 2021 12:40:09 +0200")

* Florian Weimer via Libc-alpha:

> 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").
>
> ---
> v3: Mark test as UNSUPPORTED if launching gdb fails with ENOENT.
>     This is the version I'd like to commit soon.

I've pushed this version given that Pedro acknowledged v2.

Thanks,
Florian


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 10:40 Florian Weimer
2021-04-21 11:47 ` Florian Weimer [this message]
2021-04-21 22:35   ` H.J. Lu
2021-04-22  9:29     ` Florian Weimer
2021-04-22  7:28   ` Szabolcs Nagy
2021-04-22  8:33     ` Florian Weimer
2021-04-22  9:05       ` Szabolcs Nagy
2021-04-22  9:48         ` Szabolcs Nagy
2021-04-22 11:55           ` Florian Weimer
2021-04-22 12:44             ` Szabolcs Nagy
2021-04-22 14:20               ` Szabolcs Nagy
2021-04-22 14:25                 ` Florian Weimer
2021-04-22 15:30                   ` Szabolcs Nagy
2021-04-22 15:39                     ` Florian Weimer
2021-04-22 17:22                     ` H.J. Lu
2021-04-22 17:56                       ` Florian Weimer
2021-04-22 18:27                         ` H.J. Lu
2021-04-22 14:34               ` H.J. Lu

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=87czunoo5m.fsf@oldenburg.str.redhat.com \
    --to=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).