From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix watchpoints when stepping over a breakpoint
Date: Thu, 18 Apr 2002 18:34:00 -0000 [thread overview]
Message-ID: <3CBF7449.90009@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020415090228.3798F-100000@is>
> On Sun, 14 Apr 2002, Andrew Cagney wrote:
>
>
>> As far as I can tell, the i386 backend can't locally differentiate
>> between a single step trap or a breakpoint trap.
>
>
> Really? I thought the single-step bit in EFLAGS should be set if we are
> stepping.
>
> In general, I'd love to see changes in GDB that would delegate more to
> the backend. I think GDB's application level tries to second-quess the
> target too much, which is hard without having all the target-dependent
> details. This is particularly true in the area that started this thread.
> GDB should request more information from the backend instead of trying to
> figure that out on its own, IMHO.
I suspect I need two bits of information: the stop signal and the
hardware registers. I didn't know the single-step bit would remain set.
I'll try to give it another go (but don't hold your breath :-)
Andrew
next prev parent reply other threads:[~2002-04-19 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 15:43 Daniel Jacobowitz
2002-04-04 23:38 ` Eli Zaretskii
2002-04-05 7:54 ` Daniel Jacobowitz
2002-04-05 8:45 ` Eli Zaretskii
2002-04-05 9:08 ` Daniel Jacobowitz
2002-04-05 9:55 ` Andrew Cagney
2002-04-05 23:48 ` Eli Zaretskii
2002-04-06 7:36 ` Daniel Jacobowitz
2002-04-06 9:21 ` Eli Zaretskii
2002-04-06 9:49 ` Daniel Jacobowitz
2002-04-07 9:16 ` Andrew Cagney
2002-04-07 10:03 ` Eli Zaretskii
2002-04-14 14:49 ` Andrew Cagney
2002-04-14 22:07 ` Eli Zaretskii
2002-04-18 18:34 ` Andrew Cagney [this message]
2002-04-02 22:18 Michael Elizabeth Chastain
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=3CBF7449.90009@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--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