| detailed description, instead of just the name of |
| the type. |
| For example, for this variable declaration: |
| struct complex {double real; double |
| imag;} v; |
| the two commands give this output: |
| ((gdb)) whatis v |
| type = struct complex |
| ((gdb)) ptype v |
| type = struct complex { |
| double real; |
| double imag; |
| } |
| As with whatis, using ptype without an |
| argument refers to the type of $, the last value |
| in the value history. |
info types regexp, info | Print a brief description of all types whose names |
types | match regexp (or all types in your program, if |
| you supply no argument). Each complete |
| typename is matched as though it were a |
| complete line; thus, 'i type value' gives |
| information on all types in your program whose |
| names include the string value, but 'i type |
| ^value$' gives information only on types whose |
| complete name is value. |
| This command differs from ptype in two ways: |
| first, like whatis, it does not print a detailed |
| description; second, it lists all source files where |
| a type is defined. |
info source | Show the name of the current source file―that |
| is, the source file for the function containing the |
| current point of execution―and the language it |
| was written in. |
info sources | Print the names of all source files in your |
| program for which there is debugging |
| information, organized into two lists: files whose |
| symbols have already been read, and files whose |
| symbols will be read when needed. |
info functions | Print the names and data types of all defined |
| functions. |
116 Examining the Symbol Table