Doc: valgrind with babeltrace (glib workaround)
authorJulien Desfossez <jdesfossez@efficios.com>
Tue, 16 Oct 2012 18:47:09 +0000 (14:47 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 16 Oct 2012 18:47:09 +0000 (14:47 -0400)
Signed-off-by: Julien Desfossez <jdesfossez@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
doc/Makefile.am
doc/development.txt [new file with mode: 0644]

index 597c43e79922f8d31576f2a7c06a8d44dcd692a5..6077f6232f096646f3bba32198a9f95d02cb6b72 100644 (file)
@@ -1,3 +1,5 @@
 dist_man_MANS = babeltrace.1 babeltrace-log.1
 
 dist_doc_DATA = API.txt
+
+EXTRA_DIST = development.txt
diff --git a/doc/development.txt b/doc/development.txt
new file mode 100644 (file)
index 0000000..f18070c
--- /dev/null
@@ -0,0 +1,10 @@
+This document describes some principles that should be respected when
+developing in Babeltrace.
+
+Memory usage :
+Since Babeltrace exports a library, we need to make sure that all allocated
+memory is freed, we do not want any memory leaks.
+Since Babeltrace uses the glib, it is necessary to assist a little valgrind
+when trying to identify memory leaks.
+So the proper invocation of Babeltrace with Valgrind is :
+G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --leak-check=full babeltrace
This page took 0.031996 seconds and 4 git commands to generate.