From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] debug: Remove catchsegv libSegfault
Date: Wed, 22 Dec 2021 13:57:36 +0100 [thread overview]
Message-ID: <87sfuk7q67.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <1e127167-7bc9-3f64-4002-54b8f9f42f8a@cs.ucla.edu> (Paul Eggert's message of "Tue, 21 Dec 2021 09:34:31 -0800")
* Paul Eggert:
>> I think, technically we will have to maintain libSegfault/catchsegv for
>> many years as
>
> ? This doesn't seem to match your approval of the removal.
Sorry, I meant that we'd have to maintain it separately, out of tree,
for quite a while. A deprecation followed by removal does not really
help us with that because the removal would have to be deferred to
(circa) glibc 2.41.
Thanks,
Florian
next prev parent reply other threads:[~2021-12-22 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 14:29 Adhemerval Zanella
2021-12-21 14:53 ` Florian Weimer
2021-12-21 17:34 ` Paul Eggert
2021-12-22 12:57 ` Florian Weimer [this message]
2021-12-21 17:45 ` Adhemerval Zanella
2021-12-21 18:09 ` Florian Weimer
2021-12-21 18:20 ` Adhemerval Zanella
2021-12-21 19:04 ` Joseph Myers
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=87sfuk7q67.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@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).