Lines Matching full:command
82 <term><command><computeroutput>RUNNING_ON_VALGRIND</computeroutput></command>:</term>
92 <term><command><computeroutput>VALGRIND_DISCARD_TRANSLATIONS</computeroutput>:</command></term>
117 <term><command><computeroutput>VALGRIND_COUNT_ERRORS</computeroutput>:</command></term>
130 <term><command><computeroutput>VALGRIND_MALLOCLIKE_BLOCK</computeroutput>:</command></term>
147 <term><command><computeroutput>VALGRIND_FREELIKE_BLOCK</computeroutput>:</command></term>
157 <term><command><computeroutput>VALGRIND_RESIZEINPLACE_BLOCK</computeroutput>:</command></term>
167 <command><computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput></command>,
168 <command><computeroutput>VALGRIND_DESTROY_MEMPOOL</computeroutput></command>,
169 <command><computeroutput>VALGRIND_MEMPOOL_ALLOC</computeroutput></command>,
170 <command><computeroutput>VALGRIND_MEMPOOL_FREE</computeroutput></command>,
171 <command><computeroutput>VALGRIND_MOVE_MEMPOOL</computeroutput></command>,
172 <command><computeroutput>VALGRIND_MEMPOOL_CHANGE</computeroutput></command>,
173 <command><computeroutput>VALGRIND_MEMPOOL_EXISTS</computeroutput></command>:
185 <term><command><computeroutput>VALGRIND_NON_SIMD_CALL[0123]</computeroutput>:</command></term>
195 <para><command>Warning:</command> Only use these if you
204 <term><command><computeroutput>VALGRIND_PRINTF(format, ...)</computeroutput>:</command></term>
218 <term><command><computeroutput>VALGRIND_PRINTF_BACKTRACE(format, ...)</computeroutput>:</command></term>
227 <term><command><computeroutput>VALGRIND_MONITOR_COMMAND(command)</computeroutput>:</command></term>
229 <para>Execute the given monitor command (a string).
230 Returns 0 if command is recognised. Returns 1 if command is not recognised.
234 using VALGRIND_DO_LEAK_CHECK or via the monitor command "leak_search".
235 Note that the syntax of the command string is only verified at
244 <term><command><computeroutput>VALGRIND_STACK_REGISTER(start, end)</computeroutput>:</command></term>
257 <para><command>Warning:</command> Unfortunately, this client request is
263 <term><command><computeroutput>VALGRIND_STACK_DEREGISTER(id)</computeroutput>:</command></term>
269 <para><command>Warning:</command> Unfortunately, this client request is
275 <term><command><computeroutput>VALGRIND_STACK_CHANGE(id, start, end)</computeroutput>:</command></term>
283 <para><command>Warning:</command> Unfortunately, this client request is
336 <para>Then give the following command to GDB:
343 command.</para>
348 that the command line flag <option>--vgdb=yes</option> can be omitted,
388 command line.
399 or <option>--vgdb=full</option>. A secondary command line option,
416 ==2418== Command: ./prog
453 then exit. You can then reissue the GDB "target" command, but
569 the <computeroutput>--vgdb-prefix=</computeroutput> Valgrind command
582 xreflabel="Monitor command handling by the Valgrind gdbserver">
583 <title>Monitor command handling by the Valgrind gdbserver</title>
587 sent from the GDB command line or from the shell command line or
612 <para>An example of a tool specific monitor command is the Memcheck monitor
613 command <computeroutput>leak_check full
616 command:
623 command to the Valgrind gdbserver. The Valgrind gdbserver will
624 execute the monitor command itself, if it recognises it to be a Valgrind core
625 monitor command. If it is not recognised as such, it is assumed to
645 abbreviated monitor command names and arguments, as long as the given
648 command can also be typed as:
658 unabbreviated command and arguments. If the provided abbreviation is
670 <para>Instead of sending a monitor command from GDB, you can also send
671 these from a shell command line. For example, the following command
692 GDB <computeroutput>info threads</computeroutput> command
893 <computeroutput>ldd</computeroutput> command
895 and inform GDB of the loading address using the GDB command
918 command. Debugging will not work because GDB will then not be
956 structure. To make an inferior call, use the GDB "print" command
958 example, the following GDB command causes an inferior call to the
1044 command "set remotetimeout".
1101 <title>vgdb command line options</title>
1102 <para> Usage: <computeroutput>vgdb [OPTION]... [[-c] COMMAND]...</computeroutput></para>
1111 <para>As a standalone utility, it is used from a shell command
1114 the monitor command to send. To send more than one command,
1120 <para>In combination with GDB "target remote |" command, it is
1123 COMMAND can be given.
1162 "target remote" command, you must set the GDB remotetimeout to a
1184 GDB command is suitable:
1195 to does not process a command in the specified number of seconds.
1213 <para>On the computer which hosts GDB, execute the command:
1224 <listitem><para>To give more than one command to a
1274 <para> The monitor commands can be sent either from a shell command line, by using a
1276 command (see <xref linkend="manual-core-adv.gdbserver-commandhandling"/>).
1369 command, the Valgrind process will continue the execution of the
1371 "no-op" command to a Valgrind gdbserver so as to continue the
1389 command line, then set a few breakpoints, set the vgdb-error value
1421 change this GDB behaviour by using the GDB command
1442 monitor command shows all the recorded stack traces, followed by
1444 a big number of stack traces. Typically, you will use this command
1464 command <computeroutput>info threads</computeroutput>. The output
1465 of this command shows the GDB thread number and the valgrind
1468 the callgrind tool, the callgrind monitor command
1532 The output of this command always goes to the Valgrind
1729 an object <computeroutput>libfoo.so</computeroutput> using the command
