This page was produced by an automated import process, and may have formatting errors; feel free to fix.


Fundamental Types (e.g., {{{FT_VOID}}}, {{{FT_BOOLEAN}}}).

These are the fundamental types that GDB uses internally. Fundamental types from the various debugging formats (stabs, ELF, etc) are mapped into one of these. They are basically a union of all fundamental types that GDB knows about for all the languages that GDB knows about. [Type-Codes-_0028e_002eg_002e_002c-TYPE_005fCODE_005fPTR_002c-TYPE_005fCODE_005fARRAY_0029_002e ]

Type Codes (e.g., {{{TYPE_CODE_PTR}}}, {{{TYPE_CODE_ARRAY}}}).

Each time GDB builds an internal type, it marks it with one of these types. The type may be a fundamental type, such as TYPE_CODE_INT, or a derived type, such as TYPE_CODE_PTR which is a pointer to another type. Typically, several FT_* types map to one TYPE_CODE_* type, and are distinguished by other members of the type struct, such as whether the type is signed or unsigned, and how many bits it uses. [Builtin-Types-_0028e_002eg_002e_002c-builtin_005ftype_005fvoid_002c-builtin_005ftype_005fchar_0029_002e ]

Builtin Types (e.g., {{{builtin_type_void}}}, {{{builtin_type_char}}}).

These are instances of type structs that roughly correspond to fundamental types and are created as global types for GDB to use for various ugly historical reasons. We eventually want to eliminate these. Note for example that builtin_type_int initialized in gdbtypes.c is basically the same as a TYPE_CODE_INT type that is initialized in c-lang.c for an FT_INTEGER fundamental type. The difference is that the builtin_type is not associated with any particular objfile, and only one instance exists, while c-lang.c builds as many TYPE_CODE_INT types as needed, with each one associated with some particular objfile.

None: Internals Types (last edited 2013-08-20 23:41:38 by StanShebs)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.