| /external/valgrind/main/docs/xml/ |
| manual-core.xml | 77 a suppressions file which is read when Valgrind starts up. The build
78 mechanism selects default suppressions which give reasonable
80 To make it easier to write suppressions, you can use the
81 <option>--gen-suppressions=yes</option> option. This tells Valgrind to
83 copy into a suppressions file.</para>
357 <para>You can modify and add to the suppressions file at your leisure,
364 suppressions is to use the <option>--gen-suppressions=yes</option> option
366 suppressions automatically. For best results,
368 of <option>--gen-suppressions=yes</option> by hand, in whic
[all...] |
| manual-writing-tools.xml | 234 suppressions from a suppressions file, etc. While writing these
375 <sect2 id="manual-writing-tools.suppressions" xreflabel="Suppressions">
376 <title>Suppressions</title>
379 ones, you can add suppressions to the suppression files. The relevant
|
| FAQ.xml | 494 <para>Yes! Use the <option>--gen-suppressions=yes</option> feature
495 to spit out suppressions automatically for you. You can then edit
497 suppressions using wildcards like <literal>'*'</literal>.</para>
499 <para>If you really want to write suppressions by hand, read the
546 There are some suppressions in the default suppression files.
|
| /external/valgrind/main/coregrind/ |
| m_errormgr.c | 73 suppressions file. Note that the list gets rearranged as a result
75 static Supp* suppressions = NULL; variable
208 /* Suppressions. Tools can get/set tool-relevant parts with functions
885 /* Show the used suppressions. Returns False if no suppression
896 for (su = suppressions; su != NULL; su = su->next) {
922 suppressions used. */
932 /* If we're printing XML, just show the suppressions and stop. */
[all...] |
| pub_core_errormgr.h | 3 /*--- ErrorMgr: management of errors and suppressions. ---*/
|
| m_main.c | 145 " --suppressions=<filename> suppress errors described in <filename>\n"
146 " --gen-suppressions=no|yes|all print suppressions for errors? [no]\n"
611 else if VG_STR_CLO(arg, "--suppressions", tmp_str) {
699 else if VG_XACT_CLO(arg, "--gen-suppressions=no",
701 else if VG_XACT_CLO(arg, "--gen-suppressions=yes",
703 else if VG_XACT_CLO(arg, "--gen-suppressions=all",
748 /* We can't allow --gen-suppressions=yes, since that requires us
753 (--gen-suppressions=all is still OK since we don't need any
[all...] |
| /external/valgrind/main/none/tests/ |
| cmdline2.stdout.exp | 33 --suppressions=<filename> suppress errors described in <filename>
34 --gen-suppressions=no|yes|all print suppressions for errors? [no]
|
| /external/valgrind/main/docs/html/ |
| manual-core.html | 103 a suppressions file which is read when Valgrind starts up. The build
104 mechanism selects default suppressions which give reasonable
106 To make it easier to write suppressions, you can use the
107 <code class="option">--gen-suppressions=yes</code> option. This tells Valgrind to
109 copy into a suppressions file.</p>
338 <p>You can modify and add to the suppressions file at your leisure,
344 suppressions is to use the <code class="option">--gen-suppressions=yes</code> option
346 suppressions automatically. For best results,
348 of <code class="option">--gen-suppressions=yes</code> by hand, in whic
[all...] |
| manual-writing-tools.html | 41 <dt><span class="sect2"><a href="manual-writing-tools.html#manual-writing-tools.suppressions">2.3.2. Suppressions</a></span></dt>
221 suppressions from a suppressions file, etc. While writing these
324 <div class="sect2" title="2.3.2.?Suppressions">
326 <a name="manual-writing-tools.suppressions"></a>2.3.2.?Suppressions</h3></div></div></div>
328 ones, you can add suppressions to the suppression files. The relevant
|
| tech-docs.html | 54 <dt><span class="sect2"><a href="manual-writing-tools.html#manual-writing-tools.suppressions">2.3.2. Suppressions</a></span></dt>
|
| /external/chromium/base/ |
| tools_sanity_unittest.cc | 15 // the wildcarded suppressions.
|
| /external/valgrind/tsan/ |
| Android.mk | 71 suppressions.cc \
|
| suppressions_test.cc | 30 // This file contains tests for suppressions implementation.
34 #include "suppressions.h"
52 Suppressions supp_;
346 Suppressions supp_;
|
| thread_sanitizer.h | 121 vector<string> suppressions; member in struct:FLAGS
|
| /external/valgrind/main/docs/internals/ |
| 3_1_BUGSTATUS.txt | 16 low 119446 LinuxThread error suppressions not working
108 v5382 v5481 n-i-bz AshleyP's --gen-suppressions output fix
|
| 3_2_BUGSTATUS.txt | 369 ==138507 --gen-suppressions=yes
409 r6514 r6515 32 n-i-bz Don't prompt about suppressions for unshown
463 v6011 v6029 n-i-bz amd64 padding suppressions
|
| /external/valgrind/main/ |
| glibc-2.2.supp | 173 # even more glibc suppressions ?
190 ##### suppressions for coolo
|
| xfree-3.supp | 44 # Suppressions for XFree86-3.3.X
|
| FAQ.txt | 341 Yes! Use the --gen-suppressions=yes feature to spit out suppressions
343 similar automatically generated suppressions using wildcards like '*'.
345 If you really want to write suppressions by hand, read the manual
375 some suppressions in the default suppression files. You can ignore
|
| xfree-4.supp | 7 # to X. The default suppressions are a bit of a mess and could do
380 ## More general versions of some of the old X suppressions above
|
| darwin9.supp | 2 # Suppressions for Darwin 9.x / Mac OS X 10.5 Leopard
|
| glibc-2.34567-NPTL-helgrind.supp | 6 # Suppressions for the Helgrind tool when using
|
| NEWS | 32 255822 --gen-suppressions can create invalid files: "too many callers [...]"
501 longstanding bug in which uses of suppressions against leaks were
[all...] |
| glibc-2.4.supp | 27 ## Suppressions for Fedora Core 5 on ppc32/amd64 (glibc-2.3.90)
|
| /external/valgrind/main/docs/ |
| valgrind.1 | 73 Be more verbose\&. Gives extra information on various aspects of your program, such as: the shared objects loaded, the suppressions used, the progress of the instrumentation and execution engines, and warnings about unusual behaviour\&. Repeating the option increases the verbosity level\&.
200 to restrict the plain text output to critical error messages created by Valgrind itself\&. For example, failure to read a specified suppressions file counts as a critical error message\&. In this way, for a successful run the text output file will be empty\&. But if it isn\*(Aqt empty, then it will contain important information which the GUI user should be made aware of\&.
242 An important fact about demangling is that function names mentioned in suppressions files should be in their mangled form\&. Valgrind does not demangle function names when searching for applicable suppressions, because to do otherwise would make suppression file contents dependent on the state of Valgrind\*(Aqs demangling machinery, and also slow down suppression matching\&.
314 \fB\-\-suppressions=<filename> [default: $PREFIX/lib/valgrind/default\&.supp] \fR
319 \fB\-\-gen\-suppressions=<yes|no|all> [default: no] \fR
343 This option is particularly useful with C++ programs, as it prints out the suppressions with mangled names, as required\&.
345 Note that the suppressions printed are as specific as possible\&. You may want to common up similar ones, by adding wildcards to function names, and by using frame\-level wildcards\&. The wildcarding facilities are powerful yet flexible, and with a bit of careful editing, you may be able to suppress a whole family of related errors with only a few suppressions\&.
418 \fB\-\-gen\-suppressions=yes\fR, Valgrind will stop so as to read keyboard input from you when each error occurs\&. By defa (…)
[all...] |
