This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: System call support in reversible debugging
On Fri, Nov 27, 2009 at 11:16 PM, Hui Zhu <teawater@gmail.com> wrote:
> No. ?munmap is not memory change. ?It release memory.
>
> Hui
>
> On Fri, Nov 27, 2009 at 23:11, Sean Chen <sean.chen1234@gmail.com> wrote:
>> 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
>>
>
Thanks.
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?
--
Best Regards,
Sean Chen