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 18:23:00 -0000	[thread overview]
Message-ID: <3D5DA592.8090009@ges.redhat.com> (raw)
In-Reply-To: <20020817005803.GH911@gnat.com>

> Following Andrew's suggestion, here is a revised patch to provide
> software single stepping on alpha-osf1, plus fix all the quirks that
> appeared after the switch.
> 
> I know the alpha-osf1-tdep.c change is approved, but since I haven't
> committed it yet, I am including it in this patch for completeness.
> 
> No regression on alpha-osf1 (SW single step enabled) and on x86-linux
> (sw single step disabled):

Yep, testing x68 linux is a good idea.

> 2002-07-18  Joel Brobecker  <brobecker@gnat.com>
> 
>         * alpha-osf1-tdep.c (alpha_osf1_init_abi): Unfortunately,
>         procfs appears to be broken when debugging on multi-processor
>         machines. So enable software single stepping in order to avoid
>         using the procfs interface to do next/step operations, using
>         internal breakpoints instead.
> 
>         * infrun.c (handle_inferior_event): Readjust the stop_pc by
>         DECR_PC_AFTER_BREAK when hitting a single step breakpoint, to
>         make this pc address equal to the value it would have if the
>         system stepping capability was used. Also set a new flag used
>         to ensure that we don't readjust the PC one more time later.
> 
>         * breakpoint.c (bpstat_stop_status): Do not adjust the PC
>         address by DECR_PC_AFTER_BREAK when software single step is
>         in use for this architecture, as this has already been taken
>         care of in handle_inferior_event().
> 

Yes and thanks.  Finally something in wfi that I understand!

Andrew



  reply	other threads:[~2002-08-17  1:23 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
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 [this message]
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=3D5DA592.8090009@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