diff options
Diffstat (limited to 'gdb/README')
-rw-r--r-- | gdb/README | 37 |
1 files changed, 34 insertions, 3 deletions
@@ -17,7 +17,7 @@ Unpacking and Installation -- quick overview 'gdb-VERSION.tar.gz', where VERSION is the version of GDB. The GDB debugger sources, the generic GNU include -files, the BFD ("binary file description") library, the readline +files, the BFD ("Binary File Descriptor") library, the readline library, and other libraries all have directories of their own underneath the gdb-VERSION directory. The idea is that a variety of GNU tools can share a common copy of these things. Be aware of variation @@ -417,6 +417,30 @@ more obscure GDB `configure' options are not listed here. There is no convenient way to generate a list of all available targets. +`--enable-binary-file-formats=FORMAT,FORMAT,...' +`--enable-binary-file-formats=all' + Configure GDB to only be be able to read selected file formats. + The special value "all" causes all file formats to be compiled + in, and is the the default behavior of the option. This option + is meant for advanced users who are sure of what they expect, + if you are unsure which options you will need on your debugging + sessions, we recommend that you not use this feature. The + accepted options are: + * coff: Main format on Windows systems, this is required to + compile with windows target support; + * dbx (also known as a.out): Legacy file format, this is + recommended if you know you will be dealing with this + file format; + * elf: Main format on Linux systems, this is heavily + recommended when compiling with linux support; + * macho: Main format on MacOS systems, this is heavily + recommended when compiling for those targets; + * mips (also known as ecoff): Main file format for targets + running on MIPS CPUs, this is heavily recommended when + supporting those targets; + * xcoff: Main format on AIX systems, this is required to + compile for AIX targets and rs6000 CPUs. + `--with-gdb-datadir=PATH' Set the GDB-specific data directory. GDB will look here for certain supporting files or scripts. This defaults to the `gdb' @@ -443,7 +467,14 @@ more obscure GDB `configure' options are not listed here. supported). `--disable-gdb-compile' - Build GDB without support for the 'compile' command. + Build GDB without support for the 'compile' command. DWARF support + is required for this feature. + +`--disable-gdb-dwarf-support' + Build GDB without support for reading DWARF debug information. + +`--disable-gdb-mdebug-support' + Build GDB without support for reading mdebug debug information. `--with-curses' Use the curses library instead of the termcap library, for @@ -533,7 +564,7 @@ more obscure GDB `configure' options are not listed here. GDB scripting much more powerful than the restricted CLI scripting language. If your host does not have Python installed, you can find it on `http://www.python.org/download/'. The oldest - version of Python supported by GDB is 3.2. The optional argument + version of Python supported by GDB is 3.4. The optional argument PYTHON is used to find the Python headers and libraries. It can be either the name of a Python executable, or the name of the directory in which Python is installed. |