This is the mail archive of the
mailing list for the GDB project.
Re: [Precord RFA/RFC] Check Linux sys_brk release memory in process record and replay.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Hui Zhu <teawater at gmail dot com>
- Cc: gdb-patches at sourceware dot org, msnyder at vmware dot com
- Date: Tue, 05 May 2009 21:41:08 +0300
- Subject: Re: [Precord RFA/RFC] Check Linux sys_brk release memory in process record and replay.
- References: <email@example.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 5 May 2009 21:07:13 +0800
> From: Hui Zhu <firstname.lastname@example.org>
> Cc: Michael Snyder <email@example.com>
> 15 sbrk (-10);
> The next instruction is syscall brk. It will release the memory that
> will cause process record target get error. Do you want to stop the
> inferior?([y] or n)
Does every sbrk call with a negative argument cause an error in
process record target? What is the reason for that error?
I'm asking because the message wording sounds very threatening. It
probably needs rephrasing, but I need to understand the reasons better
to suggest how.
> * gdbarch.sh (process_record_reset): This interface point to
> the function that reset the architecture process record and
I think "reset" is not the best name for this. How about