+2008-05-03 Luis Machado <luisgpm@br.ibm.com>
+ Thiago Jung Bauermann <bauerman@br.ibm.com>
+
+ * cli/cli-decode.c (lookup_cmd_1): Fix indentation.
+ * doublest.c (convert_typed_floating): Fix typo in comment.
+ * dwarf2-frame.c (dwarf2_frame_cache): Likewise.
+ * frame-unwind.h (frame_sniffer_ftype): Likewise.
+ * frame.c (frame_unwind_address_in_block): Likewise.
+ * ppc-sysv-tdep.c (ppc64_sysv_abi_push_dummy_call): Likewise.
+ * symtab.h (struct symbol): Likewise.
+ * tramp-frame.h (struct trad_frame_cache): Likewise.
+ * value.c (allocate_repeat_value): Likewise.
+
2008-05-03 Ulrich Weigand <uweigand@de.ibm.com>
* infrun.c (handle_inferior_event): Do not insert breakpoints at
flags */
if (found->flags & DEPRECATED_WARN_USER)
- deprecated_cmd_warning (&line);
+ deprecated_cmd_warning (&line);
found = found->cmd_pointer;
}
/* If we found a prefix command, keep looking. */
else
{
/* The floating-point types don't match. The best we can do
- (aport from simulating the target FPU) is converting to the
+ (apart from simulating the target FPU) is converting to the
widest floating-point type supported by the host, and then
again to the desired type. */
DOUBLEST d;
/* Then decode the insns in the FDE up to our target PC. */
execute_cfa_program (fde, fde->instructions, fde->end, this_frame, fs);
- /* Caclulate the CFA. */
+ /* Calculate the CFA. */
switch (fs->cfa_how)
{
case CFA_REG_OFFSET:
/* The following unwind functions assume a chain of frames forming the
sequence: (outer) prev <-> this <-> next (inner). All the
- functions are called with called with the next frame's `struct
- frame_info' and and this frame's prologue cache.
+ functions are called with the next frame's `struct frame_info'
+ and this frame's prologue cache.
THIS frame's register values can be obtained by unwinding NEXT
frame's registers (a recursive operation).
/* If THIS frame is not inner most (i.e., NEXT isn't the sentinel),
and NEXT is `normal' (i.e., not a sigtramp, dummy, ....) THIS
- frame's PC ends up pointing at the instruction fallowing the
+ frame's PC ends up pointing at the instruction following the
"call". Adjust that PC value so that it falls on the call
instruction (which, hopefully, falls within THIS frame's code
block). So far it's proved to be a very good approximation. See
{
/* During the first pass, GPARAM and VPARAM are more like
offsets (start address zero) than addresses. That way
- the accumulate the total stack space each region
+ they accumulate the total stack space each region
requires. */
gparam = 0;
vparam = 0;
const struct symbol_ops *ops;
/* Some symbols require additional information to be recorded on a
- per- symbol basis. Stash those values here. */
+ per-symbol basis. Stash those values here. */
union
{
/* An arbitrary data pointer. Note that this data must be
allocated using the same obstack as the symbol itself. */
/* So far it is only used by LOC_COMPUTED and LOC_COMPUTED_ARG to
- find the location location information. For a LOC_BLOCK symbol
+ find the location information. For a LOC_BLOCK symbol
for a function in a compilation unit compiled with DWARF 2
information, this is information used internally by the DWARF 2
code --- specifically, the location expression for the frame
The only way to identify a trampoline is to perform a brute force
examination of the instructions at and around the PC.
- This module provides a convent interface for performing that
+ This module provides a convenient interface for performing that
operation. */
/* A trampoline descriptor. */
}
/* Allocate a value that has the correct length
- for COUNT repetitions type TYPE. */
+ for COUNT repetitions of type TYPE. */
struct value *
allocate_repeat_value (struct type *type, int count)