Hmm, shouldn't lock your system up (hopefully it was just being unresponsive).
I tend to ssh in, cp /usr/bin/X .; sudo valgrind --trace-children=yes ./X -ac -noreset
The copy is to remove the setuid that valgrind will complain about and refuse to run.
Hmm, shouldn't lock your system up (hopefully it was just being unresponsive).
I tend to ssh in, cp /usr/bin/X .; sudo valgrind --trace- children= yes ./X -ac -noreset
The copy is to remove the setuid that valgrind will complain about and refuse to run.