<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<div style="">
<blockquote dir="auto">
<p>let's separate the fix from the mingw failure or alpine</p>
</blockquote>
<p dir="auto">That's a good choice.</p>
<p dir="auto">I still don't get why a custom signal handler is needed:</p>
<p dir="auto">man assert: <code>assert() ... terminates the program by calling abort(3)</code></p>
<p dir="auto">man abort: raises SIGABRT, but <code>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.</code></p>
<p dir="auto">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).</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777777;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/856#note_128907131">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/sent_notifications/0a45d6d6d003aaa987f8d68ad61718ce/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/856#note_128907131"}}</script>
</p>
</div>
</body>
</html>