From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>, Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix watchpoints when stepping over a breakpoint
Date: Sun, 07 Apr 2002 09:16:00 -0000 [thread overview]
Message-ID: <3CB070D6.7060902@cygnus.com> (raw)
In-Reply-To: <20020406124912.A24394@nevyn.them.org>
> No. In my original message I made a comment about shlib_event
>> > breakpoints being a problem. Other breakpoints would to. This is all
>> > because of the "watchpoint after instr, breakpoint before" thing - we
>> > would still have to deal with this, or we'd just keep hitting the same
>> > breakpoint over and over if there was a watchpoint on the next
>> > instruction.
>
>>
>> Sounds like Andrew was right: the decrement-PC logic is screwed.
>
>
> I agree. It's a rat's nest.
Only two targets use DECR_PC_AFTER_BREAK - m68k and i386. Core GDB
contans all all sorts of convoluted logic for what is a target problem :-(
What would it take to replace DECR_PC_AFTER_BREAK with a read_pc()
function that determines the stop address from the i386 hardware
registers and other state information?
(The m68k isn't multi-arch so I can fix that one by deleting it :-^)
Andrew
next prev parent reply other threads:[~2002-04-07 16:16 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 [this message]
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
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=3CB070D6.7060902@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