This is the mail archive of the gdb-patches@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: [PRecord] Memory gets set even if users responds 'n' to query

From: Hui Zhu <teawater at gmail dot com>
To: Marc Khouzam <marc dot khouzam at ericsson dot com>
Cc: Michael Snyder <msnyder at vmware dot com>, gdb-patches ml <gdb-patches at sourceware dot org>
Date: Wed, 22 Jul 2009 13:36:33 +0800
Subject: Re: [PRecord] Memory gets set even if users responds 'n' to query
References: <6D19CA8D71C89C43A057926FE0D4ADAA07C00000@ecamlmw720.eamcs.ericsson.se> <daef60380907202018s4a15735ei3bd19a2083843590@mail.gmail.com> <6D19CA8D71C89C43A057926FE0D4ADAA07C00028@ecamlmw720.eamcs.ericsson.se>

Checked in.

Thanks,
Hui

On Tue, Jul 21, 2009 at 11:38, Marc Khouzam<marc.khouzam@ericsson.com> wrote:
>> -----Original Message-----
>> From: Hui Zhu [mailto:teawater@gmail.com]
>> Sent: July-20-09 11:19 PM
>> To: Marc Khouzam; Michael Snyder
>> Cc: gdb-patches ml
>> Subject: Re: [PRecord] Memory gets set even if users responds
>> 'n' to query
>>
>> Thanks Marc.
>>
>> This issue is because when user answer n, function record_xfer_partial
>> return -1 will not really cancel the memory change operation.
>> I make a patch to change it to error.
>>
>> And I have check the code about register, it works OK. ?Because it
>> already use error.
>>
>> Please help me review it.
>
> Thanks Hui, I have tested your fix and it works for me.
>
> marc
>

References:
- Re: [PRecord] Memory gets set even if users responds 'n' to query
  - From: Hui Zhu
- RE: [PRecord] Memory gets set even if users responds 'n' to query
  - From: Marc Khouzam

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