From 03c7fcd15443f0f10845f4bfefde370b85f2edec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jiri=20Dan=C4=9Bk?= <jdanek@redhat.com>
Date: Thu, 27 Jan 2022 15:03:45 +0100
Subject: [PATCH] fixup leak:^_PyMem_RawMalloc$

---
 .github/workflows/build.yaml | 4 ++++
 tests/lsan.supp              | 1 +
 2 files changed, 5 insertions(+)

diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
index 25874e087f..dc49a4a659 100644
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -187,6 +187,10 @@ jobs:
       LD_LIBRARY_PATH: ${{github.workspace}}/install/lib
       QPID_SYSTEM_TEST_TIMEOUT: 300
       QPID_SYSTEM_TEST_SKIP_FALLBACK_SWITCHOVER_TEST: True
+      # the PyMalloc mechanism is incompatible with Valgrind, different mechanism must be set here
+      #  https://docs.python.org/3/using/cmdline.html#envvar-PYTHONMALLOC
+      #  https://pythonextensionpatterns.readthedocs.io/en/latest/debugging/debug_python.html#debug-version-of-python-memory-alloc-label
+      PYTHONMALLOC: malloc_debug
       PYTHONTRACEMALLOC: 5
     steps:
 
diff --git a/tests/lsan.supp b/tests/lsan.supp
index 77960caa29..e87792e33a 100644
--- a/tests/lsan.supp
+++ b/tests/lsan.supp
@@ -54,6 +54,7 @@ leak:^PyThread_allocate_lock$
 leak:^PyMem_Malloc$
 leak:^PyMem_Calloc$
 leak:^PyMem_Realloc$
+leak:^_PyMem_RawMalloc$
 leak:^_PyMem_RawRealloc$
 leak:^_PyObject_GC_Resize$
 # Python uses these alloc functions if you define PYTHONDEVMODE=1