From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Subject: Re: sigsegv, c-stack: Avoid compilation error with glibc >= 2.34
Date: Sun, 16 May 2021 21:45:16 -0500 [thread overview]
Message-ID: <f6d758ba-dc0a-f1b2-0cbd-ebebbb9215e1@cs.ucla.edu> (raw)
In-Reply-To: <1983155.9prZ3hhFlD@omega>
On 5/16/21 7:33 PM, Bruno Haible wrote:
> I don't have time to rewrite all these unit tests and autoconf tests.
Can we assume you wouldn't mind if someone did take the time? (Not that
I'm volunteering right just now.)
> (Additionally, if we were to use malloc() as a replacement, watch out
> that malloc()ed memory may not be executable, but some programs need
> an executable stack.)
That shouldn't be a problem on GNU platforms, since it's documented that
you can malloc the alternate signal stack. If it does turn into a
problem, I suppose we can assume that when SIGSTKSZ is not a constant
that malloc should work (otherwise how could you ever create an
alternate signal stack?).
next prev parent reply other threads:[~2021-05-17 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 0:33 sigsegv, c-stack: Avoid compilation error with glibc >= 2.34 Bruno Haible
2021-05-17 2:45 ` Paul Eggert [this message]
2021-05-18 17:34 ` Bruno Haible
2021-05-21 22:49 ` Paul Eggert
2021-05-22 22:59 ` Bruno Haible
2021-05-23 5:12 ` Paul Eggert
2021-05-23 12:14 ` Bruno Haible
2021-05-24 2:40 ` Paul Eggert
2021-05-24 10:37 ` Bruno Haible
2021-05-23 0:00 ` sigsegv.h interface Bruno Haible
2021-05-23 5:14 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6d758ba-dc0a-f1b2-0cbd-ebebbb9215e1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.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).