Lines Matching full:varname
454 information after the second line (eg. the <varname>Param</varname>
598 <para>Run the Valgrind tool called <varname>toolname</varname>,
674 initiated via the <varname>exec</varname> system call. This is
678 <varname>fork</varname> (it would be difficult not to, since
679 <varname>fork</varname> makes an identical copy of a process), so this
681 <varname>fork</varname> calls immediately call <varname>exec</varname>
735 a <varname>fork</varname> call. This can make the output less
738 with <varname>--trace-children=</varname>. Use of this option is also
740 (<varname>--xml=yes</varname>), since otherwise the XML from child and
840 command <varname>v.info open_fds</varname>. Along with each
902 environment variable <varname>FOO</varname>. If the
1421 <para>When set to <varname>yes</varname>, Valgrind will pause
1425 Pressing <varname>Ret</varname>, or <varname>N Ret</varname> or
1426 <varname>n Ret</varname>, causes Valgrind continue execution without
1429 <para>Pressing <varname>Y Ret</varname> or
1430 <varname>y Ret</varname> causes Valgrind to write a suppression
1434 <para>When set to <varname>all</varname>, Valgrind will print a
1710 <para> When set to <varname>none</varname>, no memory execution
1713 <para> When set to <varname>allocs</varname>, the memory
1717 <para> When set to <varname>full</varname>, the memory execution
1720 for <varname>allocs</varname>), the total number of allocated
1726 the value <varname>allocs</varname>, as the information needed
1728 For massif and helgrind, specifying <varname>full</varname>
1732 value <varname>full</varname> is small, as this can only be
1795 amd64 or s390x -- the default is <varname>stack</varname>.
1803 varname>all-non-file</varname>, which covers
1807 follows. No detection (<varname>none</varname>),
1810 functions) (<varname>stack</varname>), detect self-modifying code
1811 everywhere (<varname>all</varname>), and detect
1813 mappings (<varname>all-non-file</varname>).</para>
1814 <para>Running with <varname>all</varname> will slow Valgrind
1815 down noticeably. Running with <varname>none</varname> will
2413 matches <varname>sonamepatt</varname> is loaded into the
2415 those match <varname>fnnamepatt</varname>, print an error
2421 Both <varname>sonamepatt</varname> and
2422 <varname>fnnamepatt</varname> can be written using the usual
2423 <varname>?</varname> and <varname>*</varname> wildcards. For
2424 example: <varname>":*libc.so*:foo?bar"</varname>. You may use
2428 also be written <varname>"Q*libc.so*Qfoo?bar"</varname>.
2429 Multiple <varname> --require-text-symbol</varname> flags are
2436 <varname>libgomp.so</varname> which has been marked up with
2439 <varname>libgomp.so</varname> into the application. So the idea
2441 example <varname>annotated_for_helgrind_3_6</varname>, and then
2443 <varname>--require-text-symbol=:*libgomp*so*:annotated_for_helgrind_3_6</varname>
2444 so that when <varname>libgomp.so</varname> is loaded, Valgrind
2448 in quotes to stop shells expanding up the <varname>*</varname>
2449 and <varname>?</varname> wildcards.
2466 <varname>libc.so*</varname> on linux). By default, no
2483 synonym <varname>somalloc</varname>. This synonym is usable for
2493 soname <varname>mymalloclib.so</varname> (and not in any
2509 by using the <varname>NONE</varname> pattern. For example,
2510 if you link with <varname>libtcmalloc.a</varname>, and only
2532 (where <varname>nouserintercepts</varname> can be any
2540 related functions (identified by <varname>somalloc</varname> synonym).
