[epiphany/mcatanzaro/#1612: 14/14] ci: don't check for memory leaks, use-after-free, double free
- From: Marge Bot <marge-bot src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [epiphany/mcatanzaro/#1612: 14/14] ci: don't check for memory leaks, use-after-free, double free
- Date: Wed, 15 Dec 2021 19:45:46 +0000 (UTC)
commit 5c9f4bf2544c9ed447096a5aba54cbf52e4ba51e
Author: Michael Catanzaro <mcatanzaro redhat com>
Date: Wed Dec 15 13:21:44 2021 -0600
ci: don't check for memory leaks, use-after-free, double free
This is unfortunate, but the checker is too dumb. It also has no way to
suppress false positives, so we either have to make undesirable changes
to the code, or else disable the checker entirely.
We only really want to disable the memory leak checker, but there's no
way to do that without also disabling the check for use-after-free or
double free, so here we are.
My opinion of scan-build has declined drastically today. This is sad.
But it seems like the best we can do.
Part-of: <https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/1045>
.run-scan-build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/.run-scan-build b/.run-scan-build
index 88fe82454..ea778b932 100755
--- a/.run-scan-build
+++ b/.run-scan-build
@@ -2,4 +2,4 @@
set -e
-scan-build -v --status-bugs "$@"
+scan-build -v --status-bugs -disable-checker unix.Malloc "$@"
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]