Fwd: What can a signal handler do with SIGSTKSZ?
Florian Weimer
fweimer@redhat.com
Fri Jan 11 20:00:00 GMT 2019
* 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
More information about the Libc-alpha
mailing list