From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix for watchpoint regressions
Date: Mon, 21 Jun 2004 20:18:00 -0000 [thread overview]
Message-ID: <OF3C9AC52B.3B217634-ONC1256EBA.006E754A-C1256EBA.006F71C2@de.ibm.com> (raw)
Jeff Johnston wrote:
>Things worked in the past for ia64 because the code near the bottom of the
loop
>in bpstat_stop_status would check whether a hardware watchpoint value had
>changed. With Ulrich's original patch in place, this never happens
because we
>never get to that piece of code in the loop. With the revised patch, for
the
>original scenario that Ulrich was fixing, we will not get to the
watchpoint
>checking code, but for platforms that do not have
HAVE_CONTINUABLE_WATCHPOINT,
>we will. We won't yet be able to handle the breakpoint insn in code
scenario
>for ia64 that Ulrich was fixing, but that is a separate fix.
Note that my patch wasn't the first in the sequence; I only tried to fix
s390 breakage caused by the original patch (by Orjan Friberg) ...
In the past, we'd indeed always check for hardware watchpoints by comparing
all memory locations for changes. It was not my patch that changed this,
but Orjan's http://sources.redhat.com/ml/gdb-patches/2004-04/msg00521.html.
That patch was the one that tried to fix the breakpoint in code scenario.
This caused breakage on s390 because that patch unconditionally used
target_stopped_data_address; but s390 is unable to provide that info.
My change was to simply use STOPPED_BY_WATCHPOINT instead to provide
that single bit of information actually required.
But anyway, as far as s390 is concerned your patch should make no
difference, so I have no objections to it ...
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com
next reply other threads:[~2004-06-21 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 20:18 Ulrich Weigand [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 15:40 Jeff Johnston
2004-06-21 19:07 ` Eli Zaretskii
2004-06-21 19:57 ` Jeff Johnston
2004-06-22 4:24 ` Eli Zaretskii
2004-06-22 19:47 ` Jeff Johnston
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=OF3C9AC52B.3B217634-ONC1256EBA.006E754A-C1256EBA.006F71C2@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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