Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.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:12:00 -0000	[thread overview]
Message-ID: <20110310081154.GA13603@host1.jankratochvil.net> (raw)
In-Reply-To: <AANLkTimsE5nNEZ=EKo1wPs0BW9dNxdvVyu_5Fucts5K8@mail.gmail.com>

On Thu, 10 Mar 2011 08:25:18 +0100, robert song wrote:
> 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?

Watchpoints are normally created by default as hardware ones.  They should
fallback to their software variants when you get out of the number of debug
registers but that does not work well now.

You can request hardware vs. software watchpoints by using:
(gdb) help set can-use-hw-watchpoints 
Set debugger's willingness to use watchpoint hardware.
If zero, gdb will not use hardware for new watchpoints, even if
such is available.  (However, any hardware watchpoints that were
created before setting this to nonzero, will continue to use watchpoint
hardware.)

The difference is that software breakpoints are very cheap so GDB does not even
attempt to create hardware breakpoints.  While software watchpoints are very
expensive so - in fact GDB does not normally try to fallback to software ones.
When you have to use software watchpoints it is commonly even not viable to
wait for so long.


Thanks,
Jan


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  7:25 robert song
2011-03-10  8:12 ` Jan Kratochvil [this message]
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
2011-03-10  8:23 paawan oza

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=20110310081154.GA13603@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.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