diff options
Diffstat (limited to 'gdb/mdebugread.c')
| -rw-r--r-- | gdb/mdebugread.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/mdebugread.c b/gdb/mdebugread.c index dc556d6..0d63b9c 100644 --- a/gdb/mdebugread.c +++ b/gdb/mdebugread.c @@ -1319,7 +1319,7 @@ parse_symbol (SYMR *sh, union aux_ext *ax, char *ext_sh, int bigend, consequence of GDB's type management; CC and GCC (at least through version 2.4) both output variables of either type char * or caddr_t with the type - refering to the stTypedef symbol for caddr_t. If a future + referring to the stTypedef symbol for caddr_t. If a future compiler cleans this up it GDB is not ready for it yet, but if it becomes ready we somehow need to disable this check (without breaking the PCC/GCC2.4 @@ -2522,14 +2522,14 @@ parse_partial_symbols (minimal_symbol_reader &reader, /* On certain platforms, some extra label symbols can be generated by the linker. One possible usage for this kind - of symbols is to represent the address of the begining of a + of symbols is to represent the address of the beginning of a given section. For instance, on Tru64 5.1, the address of the _ftext label is the start address of the .text section. The storage class of these symbols is usually directly related to the section to which the symbol refers. For instance, on Tru64 5.1, the storage class for the _fdata - label is scData, refering to the .data section. + label is scData, referring to the .data section. It is actually possible that the section associated to the storage class of the label does not exist. On True64 5.1 |