From: Jiang Jilin <freephp@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "teawater@gmail.com" <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fixed the memory leak in record.c
Date: Fri, 28 Aug 2009 00:58:00 -0000 [thread overview]
Message-ID: <7d77a27d0908271714j7d69c551ob7791d8ef2097720@mail.gmail.com> (raw)
In-Reply-To: <4A96C677.5060402@vmware.com>
On 8/28/09, Michael Snyder <msnyder@vmware.com> wrote:
> Jiang Jilin wrote:
>> * record.c (record_list_release_next) : fixed memory leak when record
>> type is record_reg
>>
>> Signed-off-by: Jiang Jilin <freephp@gmail.com>
>
> Looks correct to me, though I'd like to hear "ok" from Hui Zhu too.
Sorry, my patch is not OK, and Hui has added a new patch. But he
hasn't checked in his new patch.
> The change is short enough to accept without a copyright assignment.
>
> For future reference, we like to see a full ChangeLog entry with a
> header that would look something like this (it's ok this time):
>
> 2009-08-27 Jiang Jilin <freephp@gmail.com>
>
> * record.c (...): ...
>
> Thank you!
I got it, thank you!
>> ---
>> gdb/record.c | 7 ++++---
>> 1 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/gdb/record.c b/gdb/record.c
>> index 8afca6b..07e9e80 100644
>> --- a/gdb/record.c
>> +++ b/gdb/record.c
>> @@ -158,9 +158,10 @@ record_list_release_next (void)
>> {
>> rec = tmp->next;
>> if (tmp->type == record_reg)
>> - record_insn_num--;
>> - else if (tmp->type == record_reg)
>> - xfree (tmp->u.reg.val);
>> + {
>> + record_insn_num--;
>> + xfree (tmp->u.reg.val);
>> + }
>> else if (tmp->type == record_mem)
>> xfree (tmp->u.mem.val);
>> xfree (tmp);
>
>
--
Regards,
Jiang
prev parent reply other threads:[~2009-08-28 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 5:26 Jiang Jilin
2009-08-27 6:34 ` Hui Zhu
2009-08-28 1:35 ` Hui Zhu
2009-08-28 1:57 ` Michael Snyder
2009-08-28 3:05 ` Hui Zhu
2009-08-27 18:28 ` Michael Snyder
2009-08-28 0:58 ` Jiang Jilin [this message]
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=7d77a27d0908271714j7d69c551ob7791d8ef2097720@mail.gmail.com \
--to=freephp@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--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