| commit | e38f4e976dd40c985bfe84230a627de9a108c9d3 | |
| author | Dmitry Frolov <frolov@swemel.ru> | |
| Fri, 25 Aug 2023 11:58:19 +0000 (25 14:58 +0300) | ||
| committer | Marc-André Lureau <marcandre.lureau@redhat.com> | |
| Mon, 4 Sep 2023 11:37:50 +0000 (4 15:37 +0400) | ||
| tree | 61d4530dcf736e14e12815072ac49035f83f7a5a | treesnapshot (tar.gz zip) |
| parent | 878490937c6273f27191e3a195c7a60fa68819b8 | commitdiff |
ui/gtk: fix leaks found wtih fuzzing
It is true, that there is no problem during runtime
from the first sight, because the memory is lost just
before qemu exits. Nevertheless, this change is necessary,
because AddressSanitizer is not able to recognize this
situation and produces crash-report (which is
false-positive in fact). Lots of False-Positive warnings
are davaluing problems, found with fuzzing, and thus the
whole methodology of dynamic analysis.
This patch eliminates such False-Positive reports,
and makes every problem, found with fuzzing, more valuable.
Fixes: 060ab76356 ("gtk: don't exit early in case gtk init fails")
Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Message-Id: <20230825115818.1091936-1-frolov@swemel.ru>
It is true, that there is no problem during runtime
from the first sight, because the memory is lost just
before qemu exits. Nevertheless, this change is necessary,
because AddressSanitizer is not able to recognize this
situation and produces crash-report (which is
false-positive in fact). Lots of False-Positive warnings
are davaluing problems, found with fuzzing, and thus the
whole methodology of dynamic analysis.
This patch eliminates such False-Positive reports,
and makes every problem, found with fuzzing, more valuable.
Fixes: 060ab76356 ("gtk: don't exit early in case gtk init fails")
Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Message-Id: <20230825115818.1091936-1-frolov@swemel.ru>
| ui/gtk.c | diffblobblamehistory |