This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fwd: What can a signal handler do with SIGSTKSZ?

From: Florian Weimer <fweimer at redhat dot com>
To: Zack Weinberg <zackw at panix dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Fri, 11 Jan 2019 21:00:29 +0100
Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ?
References: <e4215c6e-e8a4-a9b6-d88f-3c54e262711a@redhat.com> <CAKCAbMiCaBst_ofjKkH3Ck1CoOV86wPKv3QSkC89XW_zu=1BLA@mail.gmail.com> <CAKCAbMiWEk6UZJZPQb9h6GOJ5tWACMUzgg5dUra0ET4bESMotQ@mail.gmail.com>

* Zack Weinberg:

> Now, if 8192 bytes is not enough to call some async-signal-safe
> functions, that's another problem and one I would like to see
> addressed by making the unwind library more space-efficient or
> something along those lines.

Small nit: This is unrelated to async-signal-safe functions because size
considerations also apply to synchronously delivered signals, where few
(if any) restrictions exist.

Thanks,
Florian

Follow-Ups:
- Re: Fwd: What can a signal handler do with SIGSTKSZ?
  - From: Christian Brauner
- Re: Fwd: What can a signal handler do with SIGSTKSZ?
  - From: Zack Weinberg

References:
- What can a signal handler do with SIGSTKSZ?
  - From: Carlos O'Donell
- Fwd: What can a signal handler do with SIGSTKSZ?
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]