Lines Matching full:specify
686 specify more of your debugging environment at the outset.
702 You can, instead, specify a process ID as a second argument, if you
1422 the beginning of a command. Use ARGS to specify the beginning of
1533 To request debugging information, specify the `-g' option when you
1554 preprocessor macros in the debugging information if you specify the
1557 specify the options `-gdwarf-2' and `-g3'; the former option requests
1572 first specify the program name (except on VxWorks) with an
1575 Specify Files: Files.).
1592 receives from its superior. GDB provides ways to specify this
1599 Specify the arguments to give your program as the arguments of the
1661 Specify the arguments to give to your program as arguments to the
1775 Specify the arguments to be used the next time your program is
1801 The value of `PATH' used by GDB does not change. You may specify
1862 (typically the shell), but you can specify a new working directory in
1866 that specify files for GDB to operate on. *Note Commands to Specify
1905 Another way to specify where your program should do input and output
1961 `file' command to load the program. *Note Commands to Specify Files:
2221 * `set libthread-db-search-path PATH', which lets the user specify
2315 to one or more threads. Specify the numbers of the threads that
2705 Breakpoints: Set Breaks.), to specify the place where your program
2775 Set a breakpoint at the given LOCATION, which can specify a
2777 (*Note Specify
2778 specify a LOCATION.) The breakpoint will stop your program just
3355 You may also specify the system call numerically. A syscall's
3357 identify the requested service. When you specify the syscall
3541 Specify Location::, for the various forms of LOCATION; the most
3634 specified place. You can also specify a "condition" for a breakpoint.
3649 and specify a condition that tests whether the new value is an
3673 Specify EXPRESSION as the break condition for breakpoint,
3710 To make the breakpoint stop the next time it is reached, specify a
3714 breakpoint, you can specify an ignore count directly as an
3743 Specify a list of commands for the given breakpoints. The commands
3772 If the first command you specify in a command list is `silent', the
3922 optional argument IGNORE-COUNT allows you to specify a further
4065 the forms described in *note Specify Location::. This form of the
4086 described in *note Specify Location::. Execution will also stop
4468 To specify background execution, add a `&' to the command. For
4532 them (*note Specify Location::), but the effect is always to
4533 specify some source line.
4536 specify that you only want GDB to stop the program when a
4541 If you do not specify `thread THREADNO' when you set a breakpoint,
5307 for some architectures) that you specify in the `frame' command.
5348 * Specify Location:: How to specify code locations
5355 File: gdb.info, Node: List, Next: Specify Location, Up: Source
5362 specify what part of the file you want to print; see *note Specify
5401 "linespecs". Linespecs specify source lines; there are several ways of
5402 writing them (*note Specify Location::), but the effect is always to
5403 specify some source line.
5432 File: gdb.info, Node: Specify Location, Next: Edit, Prev: List, Up: Source
5437 Several GDB commands accept arguments that specify a location of your
5513 does not specify the function unambiguously, e.g., if there
5519 File: gdb.info, Node: Edit, Next: Search, Prev: Specify Location, Up: Source
5527 to specify what part of the file you want to print if you want to see
5533 file. *Note Specify Location::, for all the possible forms of the
5694 of absolute file names) or whitespace. You may specify a
5788 source line LINESPEC. You can specify source lines in any of the
5789 ways documented in *note Specify Location::.
5819 a comma, possibly surrounded by whitespace. The arguments specify
6029 `::' allows you to specify a variable in terms of the file or
6055 specify the signature of the function you want to break on, as in
6153 you can specify a static variable in a particular function or file,
6296 instruction. To do these things, specify an "output format" when you
6394 N, F, and U are all optional parameters that specify how much memory
6426 Each time you specify a unit size with `x', that size becomes the
6527 remove an expression from the list, you specify that number. The
6535 specify the output format you prefer; in fact, `display' decides
6537 uses `x' if you specify either the `i' or `s' format, or a unit size;
6564 Remove items from the list of expressions to display. Specify the
6576 enabled again later. Specify the numbers of the displays that you
6584 again in auto display of its expression, until you specify
6585 otherwise. Specify the numbers of the displays that you want
7498 specify for a program, but contains a system-dependent variety of
7552 to enable, disable, or remove a memory region, you specify that number.
7718 specify the optional keyword `binary' after the filename.
8049 specify the search pattern as a mixture of types. Note that this
8412 Using GDB's `trace' and `collect' commands, you can specify
8432 reminiscent of corefiles; you specify the filename, and use `tfind' to
8458 For each tracepoint, you can specify, in advance, some arbitrary set
8517 address in the target program. *Note Specify Location::. The
8566 addition that the user can also specify `-m MARKER' as LOCATION.
8683 reaches a specified place. You can also specify a "condition" for a
8768 `actions' without bothering about its number). You specify the
8892 specify a tracepoint number, displays information about all the
9036 tracepoint, so that you have a number with which to specify that
9529 mapped address. You can use GNU linker scripts to specify
10391 usually don't need to specify a debug format explicitly. Other
10421 You must specify `set overload-resolution off' in order to use an
10515 locations to help you specify which function definition you want.
10572 You can specify a particular definition of an overloaded symbol,
10673 you can use it to narrow the search. It is also possible to specify
10678 You must specify the complete method name, including any colons. If
11777 *note Specify Location::.
11780 specify that you only want GDB to stop the program when a
11785 If you do not specify `task TASKNO' when you set a breakpoint, the
11950 commands (*note Commands to Specify Files: Files.).
11973 specify `auto', case sensitivity is reset to the default suitable
12080 the scope defined by that location. (*Note Specify Location::, for
12225 which GDB has read some symbols. *Note Commands to Specify Files:
12398 *Note Specify Location::, for a description of the different forms
12470 frame return prematurely. If you wish to specify a value to be
12517 is required to specify the return type by an appropriate cast
12605 If you'd like to be able to patch the binary, you can specify that
12611 If you specify `set write on', GDB opens executable and core files
12612 for both reading and writing; if you specify `set write off' (the
12636 * Files:: Commands to specify files
12645 18.1 Commands to Specify Files
12648 You may want to specify executable and core dump file names. The usual
12653 GDB session. Or you may run GDB and forget to specify a file you want
12655 file: Server.). In these situations the GDB commands to specify new
12662 specify a directory and the file is not found in the GDB working
12682 Specify that the program to be run (but not the symbol table) is
12741 Specify the whereabouts of a core dump file to be used as the
12763 out for itself. You can additionally specify an arbitrary number
12765 base address for that section. You can specify any ADDRESS as an
13013 may try to load the host's libraries. GDB has two variables to specify
13166 (1) If you want to specify a local system root using a directory
13558 specify one of the
13603 file or executable target (*note Commands to Specify Files: Files.). To
13604 specify as a target a process that is already running, use the `attach'
13616 facilities. You use the argument TYPE to specify the type or
13629 (*note Commands to Specify Files: Files.).
13638 however, you can specify the file format with the `set gnutarget'
13642 _Warning:_ To specify a file format with `set gnutarget', you
13645 *Note Commands to Specify Files: Files.
13735 executable. For some object file formats, you can specify the
14321 Specify whether interrupt-sequence is sent to remote target when
15027 but without the need to specify a base address.
15836 Use these GDB commands to specify the connection to your target
15858 On some GDB host configurations, you can specify a TCP connection
16106 END-LOCATION can specify a function name, a line number, an offset
16108 address of an instruction (see *note Specify Location::, for a
16109 list of all the possible ways to specify a LOCATION.) The
16327 options, specify them via ARGS.
16478 to specify in hexadecimal.
16863 These `set' commands specify a screen height of LPP lines and a
16867 If you specify a height of zero lines, GDB does not pause during
16871 Likewise, you can specify `set width 0' to prevent GDB from
17020 `symbol-file' in *note Commands to Specify Files: Files.
17557 file is not found there, and FILENAME does not specify a directory,
17653 is printed unless you specify one.* In addition to the standard C
18037 `edit' commands do (*note Specify Location::).
19239 *Note Specify Location::.
20310 cumbersome. It may be easier to specify the scripts in the
20862 If you specify an absolute file name when prompted for the `M-x gdb'
20864 program resides. If you only specify the file name, then Emacs sets
20874 specify files for GDB to operate on. *Note Commands to Specify Files:
21072 because a command line user would not want to specify that information
21084 specify which thread and frame to operate on. To make it possible,
21123 (*note Background Execution::). The frontend may specify a preferrence
22904 by parameter. *Note Specify Location::, for a description of the
23707 provided that one does not specify NAME of that format. The command
24875 Line specification is required as parameter. *Note Specify
25121 This section describes the GDB/MI commands to specify executable file
25132 Specify the executable file to be debugged. This file is the one
25160 Specify the executable file to be debugged. Unlike
26340 /* Make sure to specify the version statically, because the
27660 This is another way to specify an argument. If this command is
27880 * Event Designators:: How to specify which history line to use.
28071 high. You will need to specify this form of printing as an option to
28172 use the `--with-libexpat-prefix' option to specify its location.
28332 `--srcdir' option to specify where to find the source. (You also need
28333 to specify a path to find `configure' itself from your working
28362 machine--the "target"). You specify a cross-debugging target by giving
28497 Specify that the default location of the system-wide init file is
28651 You can specify that GDB should always (yes) or never (no)
28655 You can specify that GDB should always (yes) or never (no)
29044 is an error to specify all processes but a specific thread, such as
29786 Specify which operations GDB expects to request of the target, as
30682 packets will follow to specify this tracepoint's actions.
30707 has an `S', then all the packets in the series specify ordinary
30758 Specify a source string of tracepoint N at address ADDR. This is
32657 Using GDB's `trace' and `collect' commands, the user can specify
33397 Alternatively, you can specify a file to read for the target
33399 commands to specify a file are:
33517 A `<compatible>' element is used to specify that the target is able
34612 Free Software Foundation. If the Program does not specify a
35138 the Document does not specify a version number of this License,
36816 * linespec: Specify Location. (line 6)
38078 * specifying location: Specify Location. (line 6)
38649 Node: Specify Location229058
