All options and
When GDB starts, it reads any arguments other than options as specifying an executable file and core file (or process ID). This is the same as if the arguments were specified by the
If GDB has not been configured to included core file support, such as for most embedded targets, then it will complain about a second argument and ignore it.
Many options have both long and short forms; both are shown in the following list. GDB also recognizes the long forms if you truncate them, so long as enough of the option is present to be unambiguous. (If you prefer, you can flag option arguments with
Read symbol table from file file.
Use file file as the executable file to execute when appropriate, and for examining pure data in conjunction with a core dump.
Read symbol table from file file and use it as the | |
| executable file. |
| |
Use file file as a core dump to examine. | |
Connect to process ID number, as with the attach | |
| command (unless there is a file in |
| named number, in which case |
| a core dump to read). |
| |
Execute GDB commands from file file. See “Command | |
| |
| |
Add directory to the path to search for source files. |
26 Getting In and Out of GDB