From dafb8da82679dcc61601d2702b0e4f1846da8101 Mon Sep 17 00:00:00 2001 From: Jeff Trawick Date: Fri, 1 Dec 2000 17:41:26 +0000 Subject: [PATCH] If apr_lock() or apr_unlock() fail, write a log message before bailing out. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87146 13f79535-47bb-0310-9956-ffa450edef68 --- server/mpm/prefork/prefork.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/server/mpm/prefork/prefork.c b/server/mpm/prefork/prefork.c index 6bee0821c6..0ee89c94f1 100644 --- a/server/mpm/prefork/prefork.c +++ b/server/mpm/prefork/prefork.c @@ -291,13 +291,19 @@ static void accept_mutex_init(apr_pool_t *p) static void accept_mutex_on(void) { apr_status_t rv = apr_lock(accept_lock); - ap_assert(!rv); + if (rv != APR_SUCCESS) { + ap_log_error(APLOG_MARK, APLOG_EMERG, rv, NULL, "couldn't grab the accept mutex"); + exit(APEXIT_CHILDFATAL); + } } static void accept_mutex_off(void) { apr_status_t rv = apr_unlock(accept_lock); - ap_assert(!rv); + if (rv != APR_SUCCESS) { + ap_log_error(APLOG_MARK, APLOG_EMERG, rv, NULL, "couldn't release the accept mutex"); + exit(APEXIT_CHILDFATAL); + } } /* On some architectures it's safe to do unserialized accept()s in the single -- 2.40.0