Re: Possible libpcp threading deadlock via pmlogger

[fche@xxxxxxxxxx (Frank Ch. Eigler)]

Nathan Scott <nathans@xxxxxxxxxx> writes:

> [...]  (perhaps interestingly, that pmlogger code is in the sigalarm
> handler, may be a clue) [...]

Just checking - are you aware of the limitations of code that may
legitimately invoked from a signal handler?  It's quite restricted.
fprintf(3) wouldn't wash, for example, and exit(3) doesn't either
(probably due to atexit()).

See also
https://www.securecoding.cert.org/confluence/display/seccode/SIG30-C.+Call+only+asynchronous-safe+functions+within+signal+handlers

- FChE