Lines Matching full:printers
7001 * Pretty-Printer Introduction:: Introduction to pretty-printers
7016 Pretty-printers are normally named. This makes them easy to manage.
7018 pretty-printers with their names. If a pretty-printer can handle
7019 multiple data types, then its "subprinters" are the printers for the
7023 Pretty-printers are installed by "registering" them with GDB.
7030 * Pretty-printers registered globally are available when debugging
7033 * Pretty-printers registered with a program space are available only
7037 * Pretty-printers registered with an objfile are loaded and unloaded
7041 *Note Selecting Pretty-Printers::, for further information on how
7042 pretty-printers are selected,
7044 *Note Writing a Pretty-Printer::, for implementing pretty printers
7082 Print the list of installed pretty-printers. This includes
7083 disabled pretty-printers, which are marked as such.
7086 pretty-printers to list. Objects can be `global', the program
7089 Selecting Pretty-Printers::, for details on how GDB looks up a
7093 printers to list.
7096 Disable pretty-printers matching OBJECT-REGEXP and NAME-REGEXP. A
7101 Enable pretty-printers matching OBJECT-REGEXP and NAME-REGEXP.
7105 Suppose we have three pretty-printers installed: one from library1.so
7124 2 of 3 printers enabled
7134 1 of 3 printers enabled
7144 0 of 3 printers enabled
17853 * Selecting Pretty-Printers:: How GDB chooses a pretty-printer.
18535 File: gdb.info, Node: Pretty Printing API, Next: Selecting Pretty-Printers, Prev: Types In Python, Up: Python API
18625 File: gdb.info, Node: Selecting Pretty-Printers, Next: Writing a Pretty-Printer, Prev: Pretty Printing API, Up: Python API
18627 23.2.2.6 Selecting Pretty-Printers
18632 pretty-printer. Printers in this list are called `global' printers,
18662 GDB provides support for enabling and disabling individual printers.
18666 Pretty-printers are enabled and disabled by attaching an `enabled'
18672 File: gdb.info, Node: Writing a Pretty-Printer, Next: Inferiors In Python, Prev: Selecting Pretty-Printers, Up: Python API
18713 We recommend that you put your core pretty-printers into a Python
18714 package. If your pretty-printers are for use with a library, we
18717 pretty-printers at the same time, because they will have different
18723 modules, followed by a call to a register pretty-printers with the
18729 GDB is able to load both sets of printers simultaneously. Then,
18730 because the search for pretty-printers is done by objfile, and because
18731 your auto-loaded code took care to register your library's printers
18732 with a specific objfile, GDB will find the correct printers for the
18748 making it hard to identify in a list of installed printers. The lookup
18757 multiple data types, then its "subprinters" are the printers for the
18769 Here are the printers:
19480 used to look up pretty-printers. A `Value' is passed to each
19519 used to look up pretty-printers. A `Value' is passed to each
20195 Missing my-foo-pretty-printers.py
20200 objfile-specific pretty-printers.
20324 * gdb.printing:: Building and registering pretty-printers.
20334 pretty-printers.
20339 Pretty-printers should generally inherit from this class.
20342 For printers that handle multiple types, this class specifies the
20346 Utility class for handling multiple printers, all recognized via
24241 Pretty-Printers::). This is done automatically when a varobj is
38867 Node: Selecting Pretty-Printers750722
