Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: teawater <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 6/10
Date: Mon, 24 Nov 2008 21:54:00 -0000	[thread overview]
Message-ID: <492AFD8F.5000800@vmware.com> (raw)
In-Reply-To: <daef60380811232308m29651103gdd9e0b7764e0220a@mail.gmail.com>

teawater wrote:
> Hi Michael,
> 
> About "record_not_record_set", It set record_not_record to let P
> record doesn't record the memory and registers control behaviors of
> GDB in function record_store_registers and record_xfer_partial.
> 
> So I think the name "record_not_record_set" and
> "record_skip_recording" are not very clear.
> Could you please give me some advices on it?

Yeah, that's pretty much the way I understood it.

It sets a one-time flag that says "omit (skip) recording
registers and memory that would otherwise be recorded".

And if I understand correctly, this is to avoid adding
changes to the record log that are made by gdb when it
resumes the target.  It's only called from "proceed()".

I'm not completely clear on what those changes are.
Is gdb modifying the PC?  Or are you perhaps trying to
avoid recording breakpoints?

Is there another way to detect and avoid recording these changes?


  reply	other threads:[~2008-11-24 19:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  2:27 teawater
2008-11-20  4:48 ` Michael Snyder
2008-11-20  5:27   ` Pedro Alves
2008-11-20  8:04     ` Michael Snyder
2008-11-20  8:08       ` Pedro Alves
2008-11-24 16:45         ` teawater
2008-11-26 17:25           ` Pedro Alves
2008-11-26 20:44             ` teawater
2008-11-24 17:32   ` teawater
2008-11-24 21:54     ` Michael Snyder [this message]
2008-11-25 17:47       ` teawater
2008-11-26 15:55         ` Michael Snyder
2008-11-26 19:32           ` teawater
2008-12-05  3:35             ` teawater
2008-12-11  3:43             ` teawater
2008-12-19  7:26 ` teawater

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=492AFD8F.5000800@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@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