From: Ben Elliston <bje@au1.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH comment in infrun.c
Date: Mon, 02 May 2005 23:42:00 -0000 [thread overview]
Message-ID: <4276BABD.8030709@au.ibm.com> (raw)
In-Reply-To: <20050502123022.GA19811@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
> It needs updating, not removal; there's still a reference in remote.c.
Better?
Index: infrun.c
===================================================================
RCS file: /home/bje/src-cvs/src/gdb/infrun.c,v
retrieving revision 1.199
diff -u -p -r1.199 infrun.c
--- infrun.c 24 Feb 2005 13:51:32 -0000 1.199
+++ infrun.c 2 May 2005 23:41:23 -0000
@@ -1233,11 +1233,10 @@ int stepped_after_stopped_by_watchpoint;
void
handle_inferior_event (struct execution_control_state *ecs)
{
- /* NOTE: cagney/2003-03-28: If you're looking at this code and
- thinking that the variable stepped_after_stopped_by_watchpoint
- isn't used, then you're wrong! The macro STOPPED_BY_WATCHPOINT,
- defined in the file "config/pa/nm-hppah.h", accesses the variable
- indirectly. Mutter something rude about the HP merge. */
+ /* NOTE: bje/2005-05-02: If you're looking at this code and thinking
+ that the variable stepped_after_stopped_by_watchpoint isn't used,
+ then you're wrong! See remote.c:remote_stopped_data_address. */
+
int sw_single_step_trap_p = 0;
int stopped_by_watchpoint = -1; /* Mark as unknown. */
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-05-02 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 6:00 Ben Elliston
2005-05-02 12:30 ` Daniel Jacobowitz
2005-05-02 23:42 ` Ben Elliston [this message]
2005-05-02 23:51 ` 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=4276BABD.8030709@au.ibm.com \
--to=bje@au1.ibm.com \
--cc=drow@false.org \
--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