summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2009-11-16 03:21:50 +0100
committerDan McGee <dan@archlinux.org>2009-11-16 03:21:50 +0100
commit8a8dfc9d55c6045d59bed6cde4ae6e2307b335ea (patch)
tree2d1a19365d6f2982f0bded22293e5be1dde6dbce
parentd2dbb04a9af7a18da217fb21b9152626c43461da (diff)
downloadpacman-8a8dfc9d55c6045d59bed6cde4ae6e2307b335ea.tar.gz
pacman-8a8dfc9d55c6045d59bed6cde4ae6e2307b335ea.tar.xz
HACKING: add some notes about valgrind/gdb usage
Signed-off-by: Dan McGee <dan@archlinux.org>
-rw-r--r--HACKING13
1 files changed, 13 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 09e782d7..537d9a37 100644
--- a/HACKING
+++ b/HACKING
@@ -133,6 +133,19 @@ For pacman:
#include "anythingelse.h"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+GDB and Valgrind Usage
+~~~~~~~~~~~~~~~~~~~~~~
+
+When using GDB or valgrind on pacman, you will want to run it on the actual
+binary rather than the shell script wrapper produced by libtool. The actual
+binary lives at `src/pacman/.libs/lt-pacman`, and will exist after running
+`./src/pacman/pacman` at least once.
+
+For example, to run valgrind:
+
+ ./src/pacman/pacman
+ valgrind --leak-check=full -- src/pacman/.libs/lt-pacman -Syu
+
/////
vim: set ts=2 sw=2 syntax=asciidoc et:
/////