From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Michael Eager <eager@eagerm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] sim: Be sure of calling freeargv() after successfully call buildargv().
Date: Mon, 02 Feb 2015 20:22:00 -0000 [thread overview]
Message-ID: <54CFDE5E.20907@sunrus.com.cn> (raw)
In-Reply-To: <54CFDB21.3050309@eagerm.com>
On 2/3/15 04:16, Michael Eager wrote:
> On 02/02/15 12:16, Chen Gang S wrote:
>>
>> If there will be no any additional reply within this week, I shall apply
>> the related 3 patches to main branch.
>>
>> Thanks.
>>
>> On 2/3/15 04:15, Chen Gang S wrote:
>>> Or there will be memory leak.
>>>
>>> 2015-02-02 Chen Gang <gang.chen.5i5j@gmail.com>
>>>
>>> * microblaze/interp.c (sim_do_command): Call freeargv() before
>
> OK to apply.
>
OK, thank. Finish "git push" for the related 3 patches.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-02-02 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 20:08 Chen Gang S
2015-02-02 20:09 ` Chen Gang S
2015-02-02 20:16 ` Michael Eager
2015-02-02 20:22 ` Chen Gang S [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-02 20:06 Chen Gang S
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=54CFDE5E.20907@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--cc=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
/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