From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [pushed] infrun.c: comment/typo fixes
Date: Thu, 25 Sep 2014 15:44:00 -0000 [thread overview]
Message-ID: <1411659876-22823-1-git-send-email-palves@redhat.com> (raw)
gdb/
2014-09-25 Pedro Alves <palves@redhat.com>
* infrun.c (stepping_past_instruction_at)
(clear_exit_convenience_vars): Point at infrun.h instead of
inferior.h.
(handle_signal_stop): Fix typo.
---
gdb/ChangeLog | 7 +++++++
gdb/infrun.c | 6 +++---
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 0efcb72..20a8a8b 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,10 @@
+2014-09-25 Pedro Alves <palves@redhat.com>
+
+ * infrun.c (stepping_past_instruction_at)
+ (clear_exit_convenience_vars): Point at infrun.h instead of
+ inferior.h.
+ (handle_signal_stop): Fix typo.
+
2014-09-24 Yao Qi <yao@codesourcery.com>
* arm-tdep.c (thumb_in_function_epilogue_p): Fix typo in the
diff --git a/gdb/infrun.c b/gdb/infrun.c
index 3725f2d..dc696e9 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -1026,7 +1026,7 @@ clear_step_over_info (void)
step_over_info.address = 0;
}
-/* See inferior.h. */
+/* See infrun.h. */
int
stepping_past_instruction_at (struct address_space *aspace,
@@ -4003,7 +4003,7 @@ handle_signal_stop (struct execution_control_state *ecs)
watchpoint expression. We do this by single-stepping the
target.
- It may not be necessary to disable the watchpoint to stop over
+ It may not be necessary to disable the watchpoint to step over
it. For example, the PA can (with some kernel cooperation)
single step over a watchpoint without disabling the watchpoint.
@@ -7124,7 +7124,7 @@ save_inferior_ptid (void)
return make_cleanup (restore_inferior_ptid, saved_ptid_ptr);
}
-/* See inferior.h. */
+/* See infrun.h. */
void
clear_exit_convenience_vars (void)
--
1.9.3
reply other threads:[~2014-09-25 15:44 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=1411659876-22823-1-git-send-email-palves@redhat.com \
--to=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).