From: "Eli Zaretskii" <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Centralize DECR_PC_AFTER_BREAK handling from infrun
Date: Sun, 18 Jan 2004 17:27:00 -0000 [thread overview]
Message-ID: <3791-Sun18Jan2004192337+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040118151909.GA17039@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 18 Jan 2004 10:19:10 -0500)
> Date: Sun, 18 Jan 2004 10:19:10 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> >
> > What happens if a location has both software and hardware
> > breakpoints? Does the code still DTRT?
>
> Hmm, I am not sure. What _is_ the right thing?
We should at least do no worse than the current code does--which is to
act as if only the first breakpoint (in the order stored in the
breakpoint data-base) were hit. That is, if breakpoints #n and #m
both fire, the current GDB announces the one whose number is smaller
(because it walks thru the breakpoints in their numerical order). It
doesn't seem to matter whether the breakpoints are of the software or
the hardware-assisted variety.
It would be nice if we could announce all breakpoints that break at
that point, but this might not be possible or very hard, I dunno.
next prev parent reply other threads:[~2004-01-18 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 22:20 Daniel Jacobowitz
2004-01-17 22:39 ` Andrew Cagney
2004-01-17 23:04 ` Daniel Jacobowitz
2004-01-18 7:05 ` Eli Zaretskii
2004-01-18 15:19 ` Daniel Jacobowitz
2004-01-18 17:27 ` Eli Zaretskii [this message]
2004-01-18 18:01 ` Andrew Cagney
2004-01-18 19:08 ` Eli Zaretskii
2004-01-31 17:51 ` Daniel Jacobowitz
2004-01-31 17:49 ` Daniel Jacobowitz
2004-01-22 14:09 ` Andrew Cagney
2004-01-22 22:34 ` Daniel Jacobowitz
2004-01-31 19:19 ` Daniel Jacobowitz
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=3791-Sun18Jan2004192337+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=drow@mvista.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