From: Michael Snyder <msnyder@vmware.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: Re: PRecord and hardware watchpoint
Date: Thu, 18 Feb 2010 18:15:00 -0000 [thread overview]
Message-ID: <4B7D83D2.6040206@vmware.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC51F301338A@EUSAACMS0703.eamcs.ericsson.se>
Marc Khouzam wrote:
> Hi,
>
> someone asked me if watchpoints worked with Reverse debugging (PRecord),
> so I gave it a try. What I found is that software watchpoints work but
> not hardware watchpoints. That sounds reasonable to me.
>
> What seemed strange was that hardware watchpoints did not work
> even when doing normal forward execution with PRecord enabled.
> I guess during replay it makes sense, but during record?
>
> Just wondering.
>
> Thanks
>
> Marc
>
> P.S. It would be nice to have some kinds of warning to tell user
> not to set hw watchpoints when PRecord is being used.
Were you using the release or CVS version?
CVS head should work.
next prev parent reply other threads:[~2010-02-18 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 17:41 Marc Khouzam
2010-02-17 18:22 ` Pedro Alves
2010-02-18 18:15 ` Michael Snyder [this message]
2010-02-19 13:51 ` Marc Khouzam
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=4B7D83D2.6040206@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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