From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org, jan.kratochvil@redhat.com,
brobecker@adacore.com
Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints
Date: Mon, 27 Dec 2010 20:18:00 -0000 [thread overview]
Message-ID: <1293462902.1544.66.camel@hactar> (raw)
In-Reply-To: <83k4ize7jx.fsf@gnu.org>
On Fri, 2010-12-24 at 13:25 +0200, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Thu, 23 Dec 2010 20:16:45 +0000
> > Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
> > Jan Kratochvil <jan.kratochvil@redhat.com>,
> > Joel Brobecker <brobecker@adacore.com>,
> > Eli Zaretskii <eliz@gnu.org>
> >
> > The resource accounting bits, I still say that they should all just
> > go away (at some point), and gdb should just try to insert the
> > watchpoint immediately, and see if the target refuses.
>
> I agree -- assuming, that is, that all the targets we support that can
> do hardware watchpoints allow us to insert the watchpoints separately
> from resuming the debuggee. If there are targets that actually insert
> the watchpoints as part as resuming the debuggee, those targets will
> be unable to tell us anything useful about the watchpoint resources
> until we actually resume the debuggee. For those targets, we will
> need to have some resource accounting in GDB, to give the user
> reasonable feedback about resource over-booking.
AFAIK breakpoint.c would have to be changed to distinguish between
software breakpoints/watchpoints and hardware breakpoints/watchpoints,
and install the latter at the moment the user creates it, and the former
would continue to be installed at the time GDB resumes the inferior, as
breakpoint.c works now.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2010-12-27 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 21:52 Thiago Jung Bauermann
2010-11-23 23:17 ` Pedro Alves
2010-11-24 21:06 ` Thiago Jung Bauermann
2010-11-25 17:32 ` Pedro Alves
2010-11-26 11:09 ` Eli Zaretskii
2010-11-27 13:25 ` Thiago Jung Bauermann
2010-11-27 15:28 ` Eli Zaretskii
2010-11-26 21:15 ` Thiago Jung Bauermann
2010-11-27 17:47 ` Pedro Alves
2010-11-27 18:01 ` Pedro Alves
2010-12-09 1:44 ` Thiago Jung Bauermann
2010-12-23 19:07 ` Thiago Jung Bauermann
2010-12-23 19:13 ` Eli Zaretskii
2010-12-23 20:17 ` Thiago Jung Bauermann
2010-12-23 22:18 ` Pedro Alves
2010-12-24 5:10 ` Joel Brobecker
2010-12-25 14:13 ` Eli Zaretskii
2010-12-27 20:18 ` Thiago Jung Bauermann [this message]
2010-12-28 2:30 ` Thiago Jung Bauermann
2010-12-28 5:47 ` Joel Brobecker
2010-12-28 16:42 ` Pedro Alves
2010-12-28 16:10 ` Pedro Alves
2010-12-29 1:00 ` Thiago Jung Bauermann
2010-11-26 10:59 ` Eli Zaretskii
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=1293462902.1544.66.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.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