Files
flatpak/common
Simon McVittie b7a18d8f98 dir: Consistently initialize g_autofree variables
All g_autofree and g_autoptr variables should be initialized, either
with a value or NULL, and some gcc versions warn if they are not.

This particular instance was harmless, because we initialized regexp
to either NULL or a valid non-NULL value as the first statement of the
function, so there was no way to return before regexp was initialized;
but if we introduced an early-return such as a g_return_val_if_fail
before the current first statement, then that early return would have
caused uninitialized stack contents to be freed, likely resulting in a
crash.

Signed-off-by: Simon McVittie <smcv@collabora.com>
(cherry picked from commit 43085c0e2a)
2023-11-14 21:27:07 +00:00
..
2019-02-25 18:12:30 +00:00
2021-02-09 09:36:59 +01:00
2018-05-24 11:59:52 +00:00
2018-10-08 08:36:23 +00:00
2022-06-16 13:49:45 +02:00
2019-04-08 12:50:42 +00:00