Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: raja.saleru@iap-online.com
Cc: gdb@sourceware.org
Subject: Re: info watch command
Date: Tue, 20 Jan 2009 13:46:00 -0000	[thread overview]
Message-ID: <20090120134645.GA26626@caradoc.them.org> (raw)
In-Reply-To: <43762.210.143.35.18.1232440582.squirrel@www.iap-online.com>

On Tue, Jan 20, 2009 at 03:36:22AM -0500, raja.saleru@iap-online.com wrote:
> by default, it will be hardware watchpoint. for the "info watch" command,
> only for watch it is showing as "hw watchpoint". however why it is not
> differentiated for rwatch as "read watchpoint" "hw read watchpoint" ?

Because all read and access watchpoints are hardware; it is not
practical to do either in software.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2009-01-20 13:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <33036.210.143.35.19.1225860010.squirrel@www.iap-online.com>
2008-11-07  7:49 ` gdb internal functionality raja.saleru
2008-11-07 12:21   ` EBo
2008-11-10 10:53     ` Jeremy Bennett
2008-11-07 18:22   ` Michael Snyder
2008-11-14  8:07 ` gdb load command flow raja.saleru
2008-11-14  8:13   ` Ramana Radhakrishnan
2008-11-14  9:07   ` Jeremy Bennett
     [not found] ` <59596.210.143.35.18.1226650013.squirrel@www.iap-online.com>
2008-11-26  1:28   ` gdb remote serial packet has wrong address raja.saleru
2008-11-26 18:46     ` Michael Snyder
     [not found]   ` <28893.210.143.35.18.1227662837.squirrel@www.iap-online.com>
2009-01-06 10:35     ` adding new commandline interface to gdb ? raja.saleru
2009-01-07  9:09       ` teawater
     [not found]     ` <17669.210.143.35.18.1231238130.squirrel@www.iap-online.com>
2009-01-20  8:36       ` info watch command raja.saleru
2009-01-20 13:46         ` Daniel Jacobowitz [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=20090120134645.GA26626@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=raja.saleru@iap-online.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