From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [commit/obv] Remove trailing space in gdbarch.sh.
Date: Wed, 12 Dec 2012 13:56:00 -0000 [thread overview]
Message-ID: <1355320564-6481-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
I noticed this trailing space when I ran an unmodified gdbarch.sh,
and yet got a difference in gdbarch.h! Fixed in gdbarch.sh.
gdb/ChangeLog:
* gdbarch.sh (software_single_step): Remove trailing space in
comment (gdbarch.h is already correct).
Checked in.
---
gdb/ChangeLog | 5 +++++
gdb/gdbarch.sh | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 7b58f00..671aa09 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2012-12-12 Joel Brobecker <brobecker@adacore.com>
+
+ * gdbarch.sh (software_single_step): Remove trailing space in
+ comment (gdbarch.h is already correct).
+
2012-12-11 Tom Tromey <tromey@redhat.com>
* dwarf2read.c (dwarf2_get_dwz_file): Set 'dwz_file'.
diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh
index 81a70b0..887552e 100755
--- a/gdb/gdbarch.sh
+++ b/gdb/gdbarch.sh
@@ -586,7 +586,7 @@ m:CORE_ADDR:addr_bits_remove:CORE_ADDR addr:addr::core_addr_identity::0
# FIXME/cagney/2001-01-18: The logic is backwards. It should be asking if the
# target can single step. If not, then implement single step using breakpoints.
#
-# A return value of 1 means that the software_single_step breakpoints
+# A return value of 1 means that the software_single_step breakpoints
# were inserted; 0 means they were not.
F:int:software_single_step:struct frame_info *frame:frame
--
1.7.10.4
next reply other threads:[~2012-12-12 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 13:56 Joel Brobecker [this message]
2012-12-12 15:33 ` Pedro Alves
2012-12-12 15:46 ` Tom Tromey
2012-12-13 5:47 ` Joel Brobecker
2012-12-13 10:32 ` Pedro Alves
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=1355320564-6481-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.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