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, 07 Jun 2004 12:42:00 -0000 [thread overview]
Message-ID: <40C46290.9000402@axis.com> (raw)
In-Reply-To: <40C45B95.9050309@axis.com>
Orjan Friberg wrote:
>
> I tried implementing a fix in handle_inferior_event (the MIPS fix is in
> proceed). It seemed easier to step one more time when we find out that
> we need to, rather than to determine beforehand that we're going to have
> to step twice (and I couldn't determine how to pass that information).
>
> The concept patch below illustrates what I'm trying to do; by setting
> another_trap in the execution control state, by the time we get to
> keep_going we won't insert the breakpoint and we'll instead continue
> single-stepping. Comments? Is this the right approach at all?
Gah. Please ignore the previous patch (and sorry); what I posted only
works when doing a continue when stopped at the branch instruction.
Doing a step (which leaves us in the delay slot) followed by another
step (or continue for that matter) prematurely inserts the breakpoint.
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-06-07 12:42 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 [this message]
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
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=40C46290.9000402@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