Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc;rfa:breakpoint] Pass full breakpoint/watchpoint count to target
Date: Mon, 30 Sep 2002 09:59:00 -0000	[thread overview]
Message-ID: <3D98830D.2070401@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020930073939.25050K-100000@is>

> On Sun, 29 Sep 2002, Andrew Cagney wrote:
> 
> 
>> The attached patch changes the target vector so that a count of each 
>> type of hardware watchpoint/breakpoint is passed to the 
>> target_can_use_hardware_breakpoints() function. (Anyone got a better 
>> name for the function?).
>> 
>> This lets targets make a better guess at how many watchpoints are going 
>> to be needed.
> 
> 
> Sorry, I don't see the large-scale picture: how will this facility be 
> used in routine GDB operations by the application-level GDB code?
> 
> Also, on a i386, for example, if you don't pass the size and alignment of 
> each address to be watched, the guess of the amount of required resources 
> can be very wrong.  This is even more exacerbated due to debug register 
> sharing implemented for i386.

Yes, see my reply to the other e-mail.  I think we can do slightly 
better with the current model.  However, to make things optimal we'll 
need to totally overhaul things.

>> The intent is for the Z? packet to pass these totals down 
>> to the target.
> 
> 
> Do you mean to say this is only for remote targets?

Other architectures can use the info.  Its just that remote will be first.

Andrew



      reply	other threads:[~2002-09-30 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 20:44 Andrew Cagney
2002-09-29 22:46 ` Eli Zaretskii
2002-09-30  9:59   ` Andrew Cagney [this message]

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=3D98830D.2070401@redhat.com \
    --to=ac131313@redhat.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