From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: [RFA] Remove redundant resetting of stepping_past_singlestep_breakpoint
Date: Tue, 02 Dec 2008 16:05:00 -0000 [thread overview]
Message-ID: <200812021604.44100.pedro@codesourcery.com> (raw)
In-Reply-To: <20081202043154.D72E81C7A0B@localhost>
On Tuesday 02 December 2008 04:31:54, Doug Evans wrote:
> Hi. While researching my prepare_to_proceed problem, I found this
> in handle_inferior_event.
>
> Just above this line:
>
> stepping_past_singlestep_breakpoint = 0;
>
> there's this:
>
> if (stepping_past_singlestep_breakpoint)
> {
> gdb_assert (singlestep_breakpoints_inserted_p);
> gdb_assert (ptid_equal (singlestep_ptid, ecs->ptid));
> gdb_assert (!ptid_equal (singlestep_ptid, saved_singlestep_ptid));
>
> stepping_past_singlestep_breakpoint = 0;
>
>
> Ok to check in?
OK.
>
> 2008-12-01 Doug Evans <dje@google.com>
>
> * infrun.c (handle_inferior_event): Remove redundant resetting of
> stepping_past_singlestep_breakpoint.
Kudos for a shorter handle_inferior_event!
--
Pedro Alves
prev parent reply other threads:[~2008-12-02 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 4:32 Doug Evans
2008-12-02 16:05 ` Pedro Alves [this message]
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=200812021604.44100.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=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