diff options
Diffstat (limited to 'gdb/dwarf2')
| -rw-r--r-- | gdb/dwarf2/frame.c | 4 | ||||
| -rw-r--r-- | gdb/dwarf2/loc.c | 2 | ||||
| -rw-r--r-- | gdb/dwarf2/read.c | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/gdb/dwarf2/frame.c b/gdb/dwarf2/frame.c index 79ef065..841d2d4 100644 --- a/gdb/dwarf2/frame.c +++ b/gdb/dwarf2/frame.c @@ -911,7 +911,7 @@ dwarf2_frame_cache (const frame_info_ptr &this_frame, void **this_cache) its return address. As a result the return address will point at some random instruction, and the CFI for that instruction is probably worthless to us. GCC's unwinder solves - this problem by substracting 1 from the return address to get an + this problem by subtracting 1 from the return address to get an address in the middle of a presumed call instruction (or the instruction in the associated delay slot). This should only be done for "normal" frames and not for resume-type frames (signal @@ -1073,7 +1073,7 @@ incomplete CFI data; unspecified registers (e.g., %s) at %s"), ULONGEST retaddr_column = fs.retaddr_column; /* It seems rather bizarre to specify an "empty" column as - the return adress column. However, this is exactly + the return address column. However, this is exactly what GCC does on some targets. It turns out that GCC assumes that the return address can be found in the register corresponding to the return address column. diff --git a/gdb/dwarf2/loc.c b/gdb/dwarf2/loc.c index 5d1a557..d515386 100644 --- a/gdb/dwarf2/loc.c +++ b/gdb/dwarf2/loc.c @@ -779,7 +779,7 @@ func_addr_to_tail_call_list (struct gdbarch *gdbarch, CORE_ADDR addr) via its tail calls (incl. transitively). Throw NO_ENTRY_VALUE_ERROR if it can call itself via tail calls. - If a funtion can tail call itself its entry value based parameters are + If a function can tail call itself its entry value based parameters are unreliable. There is no verification whether the value of some/all parameters is unchanged through the self tail call, we expect if there is a self tail call all the parameters can be modified. */ diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index 749e39d..bf9eeef 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -17882,7 +17882,7 @@ die_is_declaration (struct die_info *die, struct dwarf2_cu *cu) which value is non-zero. However, we have to be careful with DIEs having a DW_AT_specification attribute, because dwarf2_attr() (via dwarf2_flag_true_p) follows this attribute. So we may - end up accidently finding a declaration attribute that belongs + end up accidentally finding a declaration attribute that belongs to a different DIE referenced by the specification attribute, even though the given DIE does not have a declaration attribute. */ return (dwarf2_flag_true_p (die, DW_AT_declaration, cu) |