1From 0f869ec5c6bc6cd37a6803cc2299a5845199e758 Mon Sep 17 00:00:00 2001 2From: =?UTF-8?q?Marco=20Trevisan=20=28Trevi=C3=B1o=29?= <mail@3v1n0.net> 3Date: Wed, 21 Sep 2022 11:33:14 +0200 4Subject: [PATCH] regex: Use critical messages if an unexpected NULL parameter 5 is provided 6 7As programmer error we should be consistent in using criticals. 8 9Conflict:NA 10Reference:https://gitlab.gnome.org/GNOME/glib/-/commit/06caf952e48dbed40b5dcff01a94f57ba079b526c 11 12--- 13 glib/gregex.c | 2 +- 14 1 file changed, 1 insertion(+), 1 deletion(-) 15 16diff --git a/glib/gregex.c b/glib/gregex.c 17index fcc28d62f4..1baa4e2f18 100644 18--- a/glib/gregex.c 19+++ b/glib/gregex.c 20@@ -483,7 +483,7 @@ translate_match_error (gint errcode) 21 break; 22 case PCRE2_ERROR_NULL: 23 /* NULL argument, this should not happen in GRegex */ 24- g_warning ("A NULL argument was passed to PCRE"); 25+ g_critical ("A NULL argument was passed to PCRE"); 26 break; 27 case PCRE2_ERROR_BADOPTION: 28 return "bad options"; 29-- 30GitLab 31 32