| the preceding source line. This is known to occur |
| in the SunOS 4.1.1 (and earlier) C compiler. |
| GDB circumvents the problem by treating the |
| symbol scope block as starting on the previous |
| source line. |
bad string table offset in symbol n | Symbol number n contains a pointer into the |
| string table which is larger than the size of the |
| string table. |
| GDB circumvents the problem by considering |
| the symbol to have the name foo, which may |
| cause other problems if many symbols end up |
| with this name. |
unknown symbol type 0xnn | The symbol information contains new data types |
| that GDB does not yet know how to read. 0xnn |
| is the symbol type of the uncomprehended |
| information, in hexadecimal. |
| GDB circumvents the error by ignoring this |
| symbol information. This usually allows you to |
| debug your program, though certain symbols |
| are not accessible. If you encounter such a |
| problem and feel like debugging it, you can |
| debug (gdb) with itself, breakpoint on |
| complain, then go up to the function |
| read_dbx_ symtab and examine *bufp to see |
| the symbol. |
stub type has NULL name | GDB could not nd the full definition for a struct |
| or class. |
const/volatile indicator missing (ok | The symbol information for a C++ member |
if using g++ v1.x), got... | function is missing some information that recent |
| versions of the compiler should have output for |
| it. |
info mismatch between compiler | GDB could not parse a type specification output |
and debugger | by the compiler. |
132 GDB Files