From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [patch] Fix assorted typos
Date: Thu, 31 May 2007 12:19:00 -0000 [thread overview]
Message-ID: <1180613386.8837.1.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
Hi,
I've been through the internal documentation and have found a few typos.
This patch fixes those.
Best regards,
Luis
[-- Attachment #2: typos.diff --]
[-- Type: text/x-patch, Size: 5092 bytes --]
diff --git a/gdb/block.h b/gdb/block.h
index 1158dc6..59bbe03 100644
--- a/gdb/block.h
+++ b/gdb/block.h
@@ -105,7 +105,7 @@ struct block
reading. As of 16 Apr 93, this flag is never used to distinguish
between gcc2 and the native compiler.
- If there is no function corresponding to this block, this meaning
+ If there is no function corresponding to this block, the meaning
of this flag is undefined. */
unsigned char gcc_compile_flag;
diff --git a/gdb/dwarf2expr.h b/gdb/dwarf2expr.h
index c1adf9a..37c1883 100644
--- a/gdb/dwarf2expr.h
+++ b/gdb/dwarf2expr.h
@@ -46,7 +46,7 @@ struct dwarf_expr_context
void (*read_mem) (void *baton, gdb_byte *buf, CORE_ADDR addr, size_t length);
/* Return the location expression for the frame base attribute, in
- START and LENGTH. The result must be live until the current
+ START and LENGTH. The result must live until the current
expression evaluation is complete. */
void (*get_frame_base) (void *baton, gdb_byte **start, size_t *length);
@@ -59,7 +59,7 @@ struct dwarf_expr_context
/* Return the location expression for the dwarf expression
subroutine in the die at OFFSET in the current compilation unit.
- The result must be live until the current expression evaluation
+ The result must live until the current expression evaluation
is complete. */
unsigned char *(*get_subr) (void *baton, off_t offset, size_t *length);
diff --git a/gdb/dwarf2loc.c b/gdb/dwarf2loc.c
index 1e6ff67..0967da5 100644
--- a/gdb/dwarf2loc.c
+++ b/gdb/dwarf2loc.c
@@ -546,7 +546,7 @@ loclist_read_variable (struct symbol *symbol, struct frame_info *frame)
return val;
}
-/* Return non-zero iff we need a frame to evaluate SYMBOL. */
+/* Return non-zero if we need a frame to evaluate SYMBOL. */
static int
loclist_read_needs_frame (struct symbol *symbol)
{
diff --git a/gdb/frame-unwind.h b/gdb/frame-unwind.h
index e1ac871..de7fc7e 100644
--- a/gdb/frame-unwind.h
+++ b/gdb/frame-unwind.h
@@ -33,8 +33,8 @@ struct regcache;
/* 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).
diff --git a/gdb/frame.c b/gdb/frame.c
index d066a49..d3eb716 100644
--- a/gdb/frame.c
+++ b/gdb/frame.c
@@ -1502,7 +1502,7 @@ frame_unwind_address_in_block (struct frame_info *next_frame,
/* 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
diff --git a/gdb/parse.c b/gdb/parse.c
index af3ef72..60b5a4f 100644
--- a/gdb/parse.c
+++ b/gdb/parse.c
@@ -1076,7 +1076,7 @@ prefixify_subexp (struct expression *inexpr,
\f
/* This page contains the two entry points to this file. */
-/* Read an expression from the string *STRINGPTR points to,
+/* Read an expression from the string pointed by *STRINGPTR,
parse it, and return a pointer to a struct expression that we malloc.
Use block BLOCK as the lexical context for variable names;
if BLOCK is zero, use the block of the selected stack frame.
diff --git a/gdb/symtab.h b/gdb/symtab.h
index cefb0ad..ee61a98 100644
--- a/gdb/symtab.h
+++ b/gdb/symtab.h
@@ -640,7 +640,7 @@ struct symbol
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
{
@@ -649,7 +649,7 @@ struct symbol
/* 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
diff --git a/gdb/value.c b/gdb/value.c
index 26ba2a4..a88afa4 100644
--- a/gdb/value.c
+++ b/gdb/value.c
@@ -240,7 +240,7 @@ allocate_value (struct type *type)
}
/* 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)
next reply other threads:[~2007-05-31 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 12:19 Luis Machado [this message]
2007-05-31 12:40 ` Luis Machado
2007-05-31 13:06 ` Markus Deuling
2007-05-31 17:23 ` Luis Machado
2007-06-13 19:07 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180613386.8837.1.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox