summaryrefslogtreecommitdiffstats
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2021-01-26 13:14:41 +0100
committerAndreas Schneider <asn@samba.org>2021-01-29 08:42:31 +0100
commit0f8e90dd7e59c473be615dee08d445dca98fdab9 (patch)
treeae26b59bdc9b60eb10b3b503372f4f9b3852a5fe /.gitlab-ci.yml
parentc0fb86a71418dc8610089434fda4effbc99b4c12 (diff)
downloadsocket_wrapper-0f8e90dd7e59c473be615dee08d445dca98fdab9.tar.gz
socket_wrapper-0f8e90dd7e59c473be615dee08d445dca98fdab9.tar.xz
socket_wrapper-0f8e90dd7e59c473be615dee08d445dca98fdab9.zip
src/socket_wrapper.c: fix mutex fork handling
We need to use pthread_mutex_init in the child handler... See https://sourceware.org/bugzilla/show_bug.cgi?id=2745 Valgrind tools like helgrind and drd don't understand this (at least in 3.15.0), they require a pthread_mutex_unlock() in the child in order work. Pair-Programmed-With: Andreas Schneider <asn@samba.org> Signed-off-by: Stefan Metzmacher <metze@samba.org> Signed-off-by: Andreas Schneider <asn@samba.org>
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml3
1 files changed, 3 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d22bfb6..c4dd3ce 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -246,6 +246,9 @@ tumbleweed/helgrind:
when: on_failure
paths:
- obj/
+ only:
+ variables:
+ - $VALGRIND_SUPPORTS_FORKED_MUTEXES == "yes"
ubuntu/x86_64:
image: $CI_REGISTRY/$BUILD_IMAGES_PROJECT:$UBUNTU_BUILD