From: Orjan Friberg <orjan.friberg@axis.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: STEP_SKIPS_DELAY question, sort of
Date: Mon, 14 Jun 2004 12:09:00 -0000 [thread overview]
Message-ID: <40CD94F2.8050901@axis.com> (raw)
In-Reply-To: <40C73411.9060708@gnu.org>
Andrew Cagney wrote:
>
> If the:
> >> breakpoint_here_p (read_pc () - 2)
> and
> >> breakpoint_here_p (read_pc () + 4)
> logic is moved to the per-architecture STEP_SKIPS_DELAY I don't think
> DELAY_SIZE is needed.
>
> I also think this needs a new macro name that better reflects what the
> test is doing. But I've no good ideas :-/ (SINGLE_STEP_THROUGH_DELAY
> (pc)?)
SINGLE_STEP_THROUGH_DELAY sounds fine to me.
> Can a simple, separate, more explicit logic like:
> if (we just did a step and STEP_SKIPS_DELAY (pc))
> set up for another step
> return;
> work? The [handle_inferior_event patch snipped] was nested within other
> logic and that's not good from a readability / maintainability point of
> view.
Agreed; it wasn't clear from the context where I put the patch why it was there.
I'll come back with a proper patch once I've gotten around to do some more
serious testing.
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-06-14 12:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 17:14 Orjan Friberg
2004-05-21 20:25 ` Andrew Cagney
2004-05-24 9:15 ` Orjan Friberg
2004-05-24 18:15 ` Andrew Cagney
2004-05-25 11:53 ` Orjan Friberg
2004-05-25 21:14 ` Andrew Cagney
2004-05-26 9:39 ` Orjan Friberg
2004-05-26 17:39 ` Andrew Cagney
2004-06-07 12:12 ` Orjan Friberg
2004-06-07 12:42 ` Orjan Friberg
2004-06-07 13:09 ` Orjan Friberg
2004-06-07 15:08 ` Andrew Cagney
2004-06-09 9:48 ` Orjan Friberg
2004-06-09 16:00 ` Andrew Cagney
2004-06-14 12:09 ` Orjan Friberg [this message]
2004-06-16 14:53 ` Orjan Friberg
2004-06-24 18:25 ` Andrew Cagney
2004-10-01 11:26 ` Orjan Friberg
2004-10-25 20:18 ` Andrew Cagney
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=40CD94F2.8050901@axis.com \
--to=orjan.friberg@axis.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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