2014-06-02 21:21 GMT+02:00 Iñaki Baz Castillo <[email protected]>:
>> You should still be prepared to deal with EINTR, of course. Signals
>> like SIGSTOP and SIGCONT, for example, can't be blocked.
>
> Sure. But my code is mostly based on UV which already handles EINTR
> so, where should I also care about STOP and CONT?
Well, I've tried to reproduce such a possible issue (since my code
also prints to stdout/stderr and may also use syslog) by doing this:
- Run my project and generate lot of traffic in debug mode (so it logs
a lot of stuff).
- In another terminal I run:
while(true) ; do kill -STOP $(pidof myproject) ; kill -CONT
$(pidof myproject) ; done
Result? That's funny:
At the beginning I see the logs stopping and resuming (well, if I
insert a sleep between both kill calls), but then my OSX gets crazy.
Nothing responds. I cannot open a new terminal session or even
open/close applications.
PS: This has nothing to do with libuv, of course.
--
Iñaki Baz Castillo
<[email protected]>
--
You received this message because you are subscribed to the Google Groups
"libuv" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/libuv.
For more options, visit https://groups.google.com/d/optout.
