From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] enable software single step on alpha-osf
Date: Fri, 16 Aug 2002 23:29:00 -0000 [thread overview]
Message-ID: <20020817062921.GY906@gnat.com> (raw)
In-Reply-To: <3D5DA592.8090009@ges.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
> >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!
Me too. 10 lines understood, 1500 more to go :). Thanks for the careful
review.
This patch has been checked-in. Here is a patch to update the NEWS file,
as suggested by Eli. I'm not very good at wording, so any suggestion for
improvement is more than welcome.
2002-08-17 Joel Brobecker <brobecker@gnat.com>
* NEWS: Add an entry regarding the improvement of the next/step
operation on Alpha Tru64 multi-processor machines.
--
Joel
[-- Attachment #2: NEWS.diff --]
[-- Type: text/plain, Size: 672 bytes --]
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.86
diff -c -3 -r1.86 NEWS
*** NEWS 15 Aug 2002 22:51:40 -0000 1.86
--- NEWS 17 Aug 2002 06:22:04 -0000
***************
*** 91,96 ****
--- 91,102 ----
to a bfd-format or binary file (dump and append), and back
from a file into memory (restore).
+ * Improved "next/step" support on multi-processor Alpha Tru64.
+
+ On multi-processor Alpha Tru64, next/step operations sometimes used to
+ cause problems, such as the random apperance of SIGSEGV or SIGTRAP
+ signals for instance.
+
*** Changes in GDB 5.2.1:
* New targets.
next prev parent reply other threads:[~2002-08-17 6:29 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
2002-08-16 23:29 ` Joel Brobecker [this message]
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=20020817062921.GY906@gnat.com \
--to=brobecker@gnat.com \
--cc=ac131313@ges.redhat.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