From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: comment fixes in defs.h, target.c
Date: Fri, 11 Jan 2008 00:14:00 -0000 [thread overview]
Message-ID: <20080111001417.E61A61C71FC@localhost> (raw)
Checked in as obvious.
2008-01-10 Doug Evans <dje@google.com>
* defs.h (struct continuation_arg): Fix typo in comment.
* target.c (target_translate_tls_address): Fix comment spelling error.
Index: defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.214
diff -u -p -u -p -r1.214 defs.h
--- defs.h 1 Jan 2008 22:53:09 -0000 1.214
+++ defs.h 11 Jan 2008 00:09:16 -0000
@@ -706,7 +706,7 @@ extern void free_command_lines (struct c
/* To continue the execution commands when running gdb asynchronously.
A continuation structure contains a pointer to a function to be called
to finish the command, once the target has stopped. Such mechanism is
- used bt the finish and until commands, and in the remote protocol
+ used by the finish and until commands, and in the remote protocol
when opening an extended-remote connection. */
struct continuation_arg
Index: target.c
===================================================================
RCS file: /cvs/src/src/gdb/target.c,v
retrieving revision 1.152
diff -u -p -u -p -r1.152 target.c
--- target.c 1 Jan 2008 22:53:13 -0000 1.152
+++ target.c 11 Jan 2008 00:09:16 -0000
@@ -804,7 +804,7 @@ pop_target (void)
internal_error (__FILE__, __LINE__, _("failed internal consistency check"));
}
-/* Using the objfile specified in BATON, find the address for the
+/* Using the objfile specified in OBJFILE, find the address for the
current thread's thread-local storage with offset OFFSET. */
CORE_ADDR
target_translate_tls_address (struct objfile *objfile, CORE_ADDR offset)
reply other threads:[~2008-01-11 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080111001417.E61A61C71FC@localhost \
--to=dje@google.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