summaryrefslogtreecommitdiffstats
path: root/python
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2012-01-24 13:47:25 +0000
committerRichard W.M. Jones <rjones@redhat.com>2012-01-24 18:23:32 +0000
commitd2e1e8871eaf7f93ea76a7fa2fde96388d3138ea (patch)
tree312b0a0a6d3cedb311c9f3e59317a4b865213bb1 /python
parent09336d6dbb79f52d893a1b2478cc72da44772287 (diff)
downloadlibguestfs-d2e1e8871eaf7f93ea76a7fa2fde96388d3138ea.tar.gz
libguestfs-d2e1e8871eaf7f93ea76a7fa2fde96388d3138ea.tar.xz
libguestfs-d2e1e8871eaf7f93ea76a7fa2fde96388d3138ea.zip
Enable running the daemon under valgrind.
This commit allows you to run the daemon under valgrind. You have to enable it at configure time: ./configure --enable-valgrind-daemon This should *not* be done for production builds. When this feature is enabled, valgrind is added to the appliance and the daemon is run under valgrind. Log messages from valgrind are passed back over a virtio-serial channel into a file called 'valgrind.log.$PID' in the top build directory. Running 'make check', 'make extra-tests' etc causes many valgrind.log.* files to be created which must be examined by hand. (cherry picked from commit d08806adfc5d111b4b6c761540ff508d3f25b66e)
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions