Hi Ken, On Jun 4 15:36, Ken Brown wrote: > This is a followup to https://cygwin.com/ml/cygwin/2018-05/msg00334.html. > > In this patch series I attempt to implement the glibc extension > clearenv(). I also implement glibc's notion of environ==NULL being > shorthand for an empty environment. > > Two questions: > > 1. I haven't yet absorbed what SIGFE means. I arbitrarily decorated > clearenv with SIGFE rather than NOSIGFE in common.din, but I don't > know if that's right.
In a sloppy nutshell, SIGFE is for all Cygwin function calls which may call Windows functions under the hood. Anything which may take time. I.e., simple math functions or getpid(), basically immediately returning to the caller are NOSIGFE, more complex functions are SIGFE. SIGFE functions have a special function wrapper allowing to call a signal handler after the function returns. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
signature.asc
Description: PGP signature
