This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: System call support in reversible debugging

From: Michael Snyder <msnyder at vmware dot com>
To: Sean Chen <sean dot chen1234 at gmail dot com>
Cc: Hui Zhu <teawater at gmail dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Fri, 27 Nov 2009 10:07:11 -0800
Subject: Re: System call support in reversible debugging
References: <5e81cb500911262231g57f693dwc885576172e016e1@mail.gmail.com> <daef60380911270004p52c53a54k53ddab9c639db066@mail.gmail.com> <5e81cb500911270711wb99d531i111d064f05ef03b4@mail.gmail.com> <daef60380911270716r44fe2efcr79930beacc1f38ed@mail.gmail.com> <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.

Follow-Ups:
- Re: System call support in reversible debugging
  - From: Sean Chen

References:
- System call support in reversible debugging
  - From: Sean Chen
- Re: System call support in reversible debugging
  - From: Hui Zhu
- Re: System call support in reversible debugging
  - From: Sean Chen
- Re: System call support in reversible debugging
  - From: Hui Zhu
- Re: System call support in reversible debugging
  - From: Sean Chen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]