HACKING: add some notes about valgrind/gdb usage
Signed-off-by: Dan McGee <dan@archlinux.org>
This commit is contained in:
parent
d2dbb04a9a
commit
8a8dfc9d55
1 changed files with 13 additions and 0 deletions
13
HACKING
13
HACKING
|
@ -133,6 +133,19 @@ For pacman:
|
||||||
#include "anythingelse.h"
|
#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:
|
vim: set ts=2 sw=2 syntax=asciidoc et:
|
||||||
/////
|
/////
|
||||||
|
|
Loading…
Add table
Reference in a new issue