Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: Hui Zhu <teawater@gmail.com>,
	  "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: System call support in reversible debugging
Date: Sun, 29 Nov 2009 02:24:00 -0000	[thread overview]
Message-ID: <4B10154F.7070902@vmware.com> (raw)
In-Reply-To: <5e81cb500911270742j546062f2jca7441a912ffad87@mail.gmail.com>

Sean Chen wrote:

> Well. You mentioned that this munmap just can let prec ignore some
> memory change record entry. Could you please show me what kind of
> memory change is ignored?
> 
> Can gdb record the system call?

These are two separate questions.  I think the one you started with
is can gdb record a system call, and the answer is "yes".


The issue with mmap has a lot of history, and rather than try to
explain it, I urge you to look up the threads which have "mmap"
or "sbrk" in the title) and read them.


  reply	other threads:[~2009-11-27 18:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 15:11 Sean Chen
2009-11-27 15:42 ` Hui Zhu
2009-11-27 18:11   ` Sean Chen
2009-11-28  1:45     ` Hui Zhu
2009-11-28 17:44       ` Sean Chen
2009-11-29  2:24         ` Michael Snyder [this message]
2009-11-29  2:24           ` Sean Chen
2009-11-30 12:27             ` Michael Snyder
2009-11-30 16:03               ` Hui Zhu
2009-11-30 16:29                 ` Sean Chen
2009-12-01 11:32                   ` Jakob Engblom
2009-12-01 20:21                     ` Greg Law
2009-12-02 17:16                       ` Jakob Engblom
2009-12-03  3:05                         ` Sean Chen
     [not found]                   ` <4B142C54.7070207@vmware.com>
2009-12-03  2:57                     ` Sean Chen
2009-12-03  9:00                       ` Jakob Engblom
2009-12-04 15:40                         ` Sean Chen
2009-12-03 16:57                       ` Michael Snyder
2009-12-04 15:46                         ` Sean Chen

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=4B10154F.7070902@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=sean.chen1234@gmail.com \
    --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