Fix: test all close/fclose ret val, fix double close
[babeltrace.git] / doc / development.txt
CommitLineData
49636689
JD
1This document describes some principles that should be respected when
2developing in Babeltrace.
3
4Memory usage :
5Since Babeltrace exports a library, we need to make sure that all allocated
6memory is freed, we do not want any memory leaks.
7Since Babeltrace uses the glib, it is necessary to assist a little valgrind
8when trying to identify memory leaks.
9So the proper invocation of Babeltrace with Valgrind is :
10G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --leak-check=full babeltrace
This page took 0.022397 seconds and 4 git commands to generate.