Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] enable software single step on alpha-osf
Date: Fri, 16 Aug 2002 12:11:00 -0000	[thread overview]
Message-ID: <3D5D4E46.7080902@ges.redhat.com> (raw)
In-Reply-To: <20020816182141.GJ906@gnat.com>


> So, to summarize: 
> 
>   1 - The change "+           stop_pc -= DECR_PC_AFTER_BREAK;" seems
>       to be going in the right direction.
> 
>   2 - However I should hold this change for now because you think I should
>       write the adjusted PC value back to the target, by adding something
>       like "write_pc_pid (stop_pc, ecs->ptid)"
> 
>       I will verify the impact of such a change, and report.
>     
>   3 - Assuming we get all issues in this RFA resolved, then I will start
>       looking at the addition of the software_singlestep flag.

I think the flag should be added as part of the change.  That way we're 
100% certain that bpstat_stop_status() isn't going to do a 
decr_pc_after_break.

Expressions like:

/* Pass TRUE if our reason for stopping is something other
    than hitting a breakpoint.  We do this by checking that
    1) stepping is going on and 2) we didn't hit a breakpoint
    in a signal handler without an intervening stop in
    sigtramp, which is detected by a new stack pointer value
    below any usual function calling stack adjustments.  */
(currently_stepping (ecs)
  && prev_pc != stop_pc - DECR_PC_AFTER_BREAK
  && !(step_range_end && INNER_THAN (read_sp (),(step_sp - 16)))));

would be changed to read:

(trap_was_a_software_singlestep
  || ....)

Hmm, looking at the above, on an architecture like the i386, the test 
``prev_pc != stop_pc - DECR_PC_AFTER_BREAK'' is probably false when if 
the code has just stepped off a single byte instruction :-(

enjoy,
Andrew



  reply	other threads:[~2002-08-16 19:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 13:55 Joel Brobecker
2002-07-22  4:19 ` Eli Zaretskii
2002-07-25 16:38 ` Andrew Cagney
2002-07-26 10:17   ` Jason R Thorpe
2002-07-31 10:28     ` Joel Brobecker
2002-08-04 16:42 ` Andrew Cagney
2002-08-05 11:49   ` Joel Brobecker
2002-08-05 20:01     ` Andrew Cagney
2002-08-16 10:11     ` Andrew Cagney
2002-08-16 11:21       ` Joel Brobecker
2002-08-16 12:11         ` Andrew Cagney [this message]
2002-08-16 12:26           ` Daniel Jacobowitz
2002-08-16 12:40             ` Kevin Buettner
2002-08-16 14:40               ` Peter.Schauer
2002-08-16 12:41             ` Andrew Cagney
2002-08-16 16:05         ` Joel Brobecker
2002-08-16 16:45           ` Andrew Cagney
2002-08-16 17:58             ` Joel Brobecker
2002-08-16 18:23               ` Andrew Cagney
2002-08-16 23:29                 ` Joel Brobecker
2002-08-20  8:55                   ` Joel Brobecker
2002-08-20 17:29                     ` Andrew Cagney
2002-08-20 19:14                       ` Daniel Jacobowitz
2002-08-21  7:01                         ` Joel Brobecker

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=3D5D4E46.7080902@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=brobecker@gnat.com \
    --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