From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFC: Centralize DECR_PC_AFTER_BREAK handling from infrun
Date: Sun, 18 Jan 2004 19:08:00 -0000 [thread overview]
Message-ID: <9787-Sun18Jan2004210346+0200-eliz@elta.co.il> (raw)
In-Reply-To: <400AC9D4.1020104@gnu.org> (message from Andrew Cagney on Sun, 18 Jan 2004 13:00:52 -0500)
> Date: Sun, 18 Jan 2004 13:00:52 -0500
> From: Andrew Cagney <cagney@gnu.org>
> >
> > 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.
>
> I'm not that sure that the current code is right though :-(
Me neither. That's why I think we should try to do better if it's
reasonable. But we shouldn't make things worse, at the very least.
> I recall comlaints about the current behavior - it should report all
> possible reasons for breaking and not just the first.
Sure, and the commands bound to all breakpoints should certainly be
run, which we don't currently do. That's a bug.
next prev parent reply other threads:[~2004-01-18 19:08 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
2004-01-18 18:01 ` Andrew Cagney
2004-01-18 19:08 ` Eli Zaretskii [this message]
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=9787-Sun18Jan2004210346+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--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