Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Florian Weimer via Gdb-patches <gdb-patches@sourceware.org>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Pedro Alves <palves@redhat.com>,
	Emil Velikov via Libc-alpha <libc-alpha@sourceware.org>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v2] nptl_db: Support different libpthread/ld.so load orders (bug 27744)
Date: Tue, 27 Apr 2021 14:11:41 +0200	[thread overview]
Message-ID: <875z08nczm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CACvgo53OfLcVR3U8q+AgX8_kg3dAL4TxKyNY=JJk2tx8-oRD0A@mail.gmail.com> (Emil Velikov's message of "Tue, 27 Apr 2021 12:46:56 +0100")

* Emil Velikov:

> On Mon, 19 Apr 2021 at 11:57, Florian Weimer <fweimer@redhat.com> wrote:
>
>> > Are there any plans for glibc 2.33.1 or shall I ask the Arch Linux
>> > maintainers to include this in the package?
>>
>> I'm going to backport it to the release branch, but we probably won't
>> make an actual 2.33.1 release from it.  So it depends on what Arch Linux
>> does with the release branch.

> I can see the patch landed in master \o/ but it's missing in the 2.33 branch.
> Did it slip through the cracks or you're simply EBUSY with the
> nptl/c11 pthread to libc transition?

I wanted to give it a test in Fedora rawhide, but we cannot rebuild
glibc there due to an unrelated issue right now.

I can backport it blindly if it helps.

Thanks,
Florian


  reply	other threads:[~2021-04-27 12:11 UTC|newest]

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

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=875z08nczm.fsf@oldenburg.str.redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palves@redhat.com \
    /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