From: Sean Chen <sean.chen1234@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: System call support in reversible debugging
Date: Fri, 27 Nov 2009 18:11:00 -0000 [thread overview]
Message-ID: <5e81cb500911270711wb99d531i111d064f05ef03b4@mail.gmail.com> (raw)
In-Reply-To: <daef60380911270004p52c53a54k53ddab9c639db066@mail.gmail.com>
On Fri, Nov 27, 2009 at 4:04 PM, Hui Zhu <teawater@gmail.com> wrote:
> This is a old query. For now, this munmap just can let prec ignore
> some memory change record entry.
>
> You can answer 'no' then inferior will keep exec. Most of thing will
> be find. :)
>
> Maybe we need update this query looks not so scary and do some other update.
>
> Thanks,
> Hui
>
> On Fri, Nov 27, 2009 at 14:31, Sean Chen <sean.chen1234@gmail.com> wrote:
>> Hi,
>>
>> Can gdb record system calls without checkpoints or snapshots
>> currently? If not, is it possible to record the instructions and
>> reverse the inferior?
>>
>> When I recorded fclose(), I got the following message.
>> The next instruction is syscall munmap. It will free the memory addr
>> = 0xb7fe0000 len = 4096. It will make record target get error. Do
>> you want to stop the program?([y] or n)
>>
>> Thanks in advance.
>>
>> --
>> Best Regards,
>> Sean Chen
>>
>
Thanks for your reply.
Does it mean that we have to ignore all memory changes in all system
calls or kernel space code?
--
Best Regards,
Sean Chen
next prev parent reply other threads:[~2009-11-27 15: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 [this message]
2009-11-28 1:45 ` Hui Zhu
2009-11-28 17:44 ` Sean Chen
2009-11-29 2:24 ` Michael Snyder
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=5e81cb500911270711wb99d531i111d064f05ef03b4@mail.gmail.com \
--to=sean.chen1234@gmail.com \
--cc=gdb@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