commit c5f6862b726bde92fc224c3716d8d854e04c84e7
Author: Laszlo Papp <>
Date:   Tue Nov 17 00:08:50 2009 +0100

HACKING: Modify some notes about valgrind/gdb usage

* Remove trace-children; It will be clean instead of taking decision
manually which error output counts and which one not

* Running src/pacman-g2/.libs/pacman-g2 will cause you to use the
libpacman installed on the system and not the one built in the source tree.
You need to run lt-pacman-g2 instead

diff --git a/HACKING b/HACKING
index 652a886..e1c3fd7 100644
@@ -25,14 +25,17 @@ cd pactest; python --test=tests/ -p 
That's all.

How to test pacman-g2 more using valgrind?

-Try to run some commands using valgrind with a command like:
+When using GDB or valgrind on pacman-g2, 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-g2/.libs/lt-pacman-g2, and will exist after running
+`./src/pacman-g2/pacman-g2` at least once.

-valgrind --leak-check=full --trace-children=yes -- src/pacman-g2/pacman-g2 -Syu
+For example, to run valgrind:

-Be careful, valgrind reports lots of errors, even some errors that may not be 
related to
-pacman-g2. You should have a little experience of valgrind to ignore the noise.
+    ./src/pacman-g2/pacman-g2
+    valgrind --leak-check=full -- src/pacman-g2/.libs/lt-pacman-g2 -Syu

How should I make benchmarks?
Frugalware-git mailing list

Reply via email to