From: Julian Seward Date: Fri, 7 Dec 2012 08:40:16 +0000 (+0000) Subject: Add documentation for --extra-debuginfo-path=. Relates to #310972. X-Git-Tag: svn/VALGRIND_3_9_0~503 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bb446d67bb3c786808df76c4f407070219129cee;p=thirdparty%2Fvalgrind.git Add documentation for --extra-debuginfo-path=. Relates to #310972. (Alex Chiang, achiang@canonical.com) git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13169 --- diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index 7b8a77f817..772ac52694 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -1130,6 +1130,39 @@ that can report errors, e.g. Memcheck, but not Cachegrind. + + + + + + By default Valgrind searches in several well-known paths + for debug objects, such + as /usr/lib/debug/. + + However, there may be scenarios where you may wish to put + debug objects at an arbitrary location, such as external storage + when running Valgrind on a mobile device with limited local + storage. Another example might be a situation where you do not + have permission to install debug object packages on the system + where you are running Valgrind. + + In these scenarios, you may provide an absolute path as an extra, + final place for Valgrind to search for debug objects by specifying + . + The given path will be prepended to the absolute path name of + the searched-for object. For example, if Valgrind is looking + for the debuginfo + for /w/x/y/zz.so + and is specified, + it will look for a debug object at + /a/b/c/w/x/y/zz.so. + + This flag should only be specified once. If it is + specified multiple times, only the last instance is + honoured. + + +