Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: robert song <robertsong.japan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Why no hwatch command in gdb ?
Date: Thu, 10 Mar 2011 08:23:00 -0000	[thread overview]
Message-ID: <945241.43722.qm@web112504.mail.gq1.yahoo.com> (raw)



gdb uses HW debug registers HW support is there; and most of the processors have 

it.

just need to change configuration internal to gdb;

set can-use-hw-watchpoint.. 1


then when you watch; it will set as many watchpoints as many debug registers 
available.

regards,
Oza.



----- Original Message ----
From: robert song <robertsong.japan@gmail.com>
To: gdb@sourceware.org
Sent: Thu, March 10, 2011 12:55:18 PM
Subject: Why no hwatch command in gdb ?

Hi, everyone.

In gdb command line, we can use break or hbreak to set breakpoint or
hardware breakpoint.

But I can only find watch command without hardware watch command, so
why watchpoint and breakpoint command are not united?

Regards,
  robert


      


             reply	other threads:[~2011-03-10  8:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  8:23 paawan oza [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10  7:25 robert song
2011-03-10  8:12 ` Jan Kratochvil
2011-03-10 10:09   ` robert song
2011-03-10 10:34     ` Jan Kratochvil
2011-03-10 11:26       ` Eli Zaretskii
2011-03-10 11:34         ` Joel Brobecker
2011-03-10 12:27           ` Pedro Alves
2011-03-10 11:55         ` Jan Kratochvil
2011-03-10 14:47           ` Frank Ch. Eigler
2011-03-10 12:18       ` robert song
2011-03-10 13:45         ` Jan Kratochvil
2011-03-10 14:47           ` Philippe Waroquiers
2011-03-10 21:04             ` Tom Tromey
2011-03-11  7:58               ` Philippe Waroquiers
2011-03-11 17:48           ` 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=945241.43722.qm@web112504.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=gdb@sourceware.org \
    --cc=robertsong.japan@gmail.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