[pygobject] Run tests with G_SLICE=debug_blocks
- From: Martin Pitt <martinpitt src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [pygobject] Run tests with G_SLICE=debug_blocks
- Date: Wed, 27 Feb 2013 20:59:03 +0000 (UTC)
commit a51c72c771dafc0c13d7990f1ff3e428dca729a1
Author: Martin Pitt <martinpitt gnome org>
Date: Wed Feb 27 21:51:30 2013 +0100
Run tests with G_SLICE=debug_blocks
This will help finding regressions in slice management, like in
https://bugzilla.gnome.org/show_bug.cgi?id=691501
tests/Makefile.am | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 263e533..140fa2b 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -126,6 +126,7 @@ RUN_TESTS_ENV_VARS= \
XDG_DATA_DIRS=$$XDG_DATA_DIRS:/usr/share \
MALLOC_PERTURB_=85 \
MALLOC_CHECK_=3 \
+ G_SLICE=debug-blocks \
TESTS_BUILDDIR=$(builddir)
# pygtkcompat tests need to be run in a separate process as they
@@ -150,4 +151,4 @@ check.nemiver:
EXEC_NAME="nemiver" $(MAKE) check
check.valgrind:
- EXEC_NAME="valgrind --leak-check=full --show-possibly-lost=no --suppressions=python.supp"
G_SLICE=always-malloc G_DEBUG=gc-friendly $(MAKE) check
+ EXEC_NAME="valgrind --leak-check=full --show-possibly-lost=no --suppressions=python.supp"
G_DEBUG=gc-friendly $(MAKE) check
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]