From 4308c868f94df1f2b99e80038ba5ea1076d919a7 Mon Sep 17 00:00:00 2001 From: Anatol Belski Date: Thu, 14 Jan 2016 17:42:28 +0100 Subject: [PATCH] Fixed bug #70979 crash with bad soap request The error handler is overloaded with the SOAP one. However the SOAP handler eventually wants to access some of its globals. This won't work as long as the SOAP globals aren't initialized. The use case is when an error is thrown before RINIT went through. As the call order is arbitrary, the safest is to wait when all the modules called their RINIT. --- ext/soap/soap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ext/soap/soap.c b/ext/soap/soap.c index 7c84bc9adb..f0e26bf19d 100644 --- a/ext/soap/soap.c +++ b/ext/soap/soap.c @@ -2135,7 +2135,7 @@ static void soap_error_handler(int error_num, const char *error_filename, const _old_http_response_code = SG(sapi_headers).http_response_code; _old_http_status_line = SG(sapi_headers).http_status_line; - if (!SOAP_GLOBAL(use_soap_error_handler) || !EG(objects_store).object_buckets) { + if (!PG(modules_activated) || !SOAP_GLOBAL(use_soap_error_handler) || !EG(objects_store).object_buckets) { call_old_error_handler(error_num, error_filename, error_lineno, format, args); return; } -- 2.40.0