From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Yuri <yuri@rawbw.com>
Cc: gdb@sourceware.org
Subject: Re: Why gdb-7.1 doesn't set hardware watchpoints on i7 CPU (amd64)?
Date: Thu, 30 Jun 2011 22:50:00 -0000 [thread overview]
Message-ID: <CALoOobPkcR6zJXXYQ3O-bP=gwW0CoyGLkfNhbC5k1n8xbnDQ-g@mail.gmail.com> (raw)
In-Reply-To: <4E0CF948.6030303@rawbw.com>
On Thu, Jun 30, 2011 at 3:31 PM, Yuri <yuri@rawbw.com> wrote:
> On 12/26/2010 21:06, Paul Pluzhnikov wrote:
>>
>> You begin by explaining what made you conclude that you can't set HW
>> watchpoints, preferably by showing a sample program and a complete log
>> of your GDB session. Verifying that the same problem exists in current
>> CVS snapshot is also a good idea.
You didn't show *complete* log of your GDB session.
This leaves us to guess which version of GDB you are using (your message
says 7.2), and what platform it was configured for.
Verifying that the problem exists in latest CVS snapshot is *still*
a good idea.
> This happens on all programs.
> I "conclude" by seeing that it prints "Watchpoint" not "Hardware watchpoint"
> and observing a very slow execution after it is set.
>
> (gdb) watch *(char*)0x3c74340
> Watchpoint 6: *(char*)0x3c74340
> (gdb) c
> <...very long wait...>
Is 0x3c74340 addressable at the point where you set the watch?
(This also likely would have been answered by a complete log of your
GDB session.)
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-06-30 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 3:20 Yuri
2010-12-27 5:07 ` Paul Pluzhnikov
2011-06-30 22:31 ` Yuri
2011-06-30 22:50 ` Paul Pluzhnikov [this message]
2011-06-30 23:40 ` Yuri
2011-07-01 10:02 ` Pedro Alves
2011-06-30 22:27 ` Yuri
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='CALoOobPkcR6zJXXYQ3O-bP=gwW0CoyGLkfNhbC5k1n8xbnDQ-g@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=yuri@rawbw.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