[gnutls-devel] GnuTLS | tests: treat all signals as error (!856)
Development of GNU's TLS library
gnutls-devel at lists.gnutls.org
Fri Jan 4 10:03:34 CET 2019
> let's separate the fix from the mingw failure or alpine
That's a good choice.
I still don't get why a custom signal handler is needed:
man assert: `assert() ... terminates the program by calling abort(3)`
man abort: raises SIGABRT, but `If the SIGABRT signal is ignored, or caught by a handler that returns, the abort() function will still terminate the process. It does this by restoring the default disposition for SIGABRT and then raising the signal for a second time.`
This is POSIX behavior. If glibc doesn't behave like this, it is a bug. If it does, I don't understand why the code sets a variable in a signal handler. A check after a failed assert() doesn't make sense (except as a work-around for buggy glibc behavior).
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/856#note_128907131
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnutls-devel