From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [ob] printcmd.c (build_address_symbolic): Fix comment.
Date: Thu, 26 Feb 2009 01:17:00 -0000 [thread overview]
Message-ID: <20090225182827.28A4B1C78A4@localhost> (raw)
Hi.
Checked in under the obvious rule.
2009-02-25 Doug Evans <dje@google.com>
* printcmd.c (build_address_symbolic): Fix comment.
Index: printcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/printcmd.c,v
retrieving revision 1.143
diff -u -p -r1.143 printcmd.c
--- printcmd.c 25 Feb 2009 02:14:22 -0000 1.143
+++ printcmd.c 25 Feb 2009 18:26:12 -0000
@@ -604,7 +604,7 @@ build_address_symbolic (CORE_ADDR addr,
struct obj_section *section = NULL;
char *name_temp = "";
- /* Let's say it is unmapped. */
+ /* Let's say it is mapped (not unmapped). */
*unmapped = 0;
/* Determine if the address is in an overlay, and whether it is
reply other threads:[~2009-02-25 18:28 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=20090225182827.28A4B1C78A4@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