Well, the recent version runs ok, I just wan't to find the commit solving this bug.
Thanks, Zongyong Wu -----邮件原件----- 发件人: Eduardo Bustamante [mailto:dual...@gmail.com] 发送时间: 2017年5月11日 22:39 收件人: wuzongyong (A) <wuzongyo...@huawei.com> 抄送: bug-bash@gnu.org; Wanzongshun (Vincent) <wanzongs...@huawei.com> 主题: Re: memory leak in bash On Thu, May 11, 2017 at 3:47 AM, wuzongyong (A) <wuzongyo...@huawei.com> wrote: [...] > My bash version is version 4.2.46(1)-release, valgrind version is 3.11.0 , > could someone help to tell me if it is a bug please? And I wanna to know the > deeply level reason. Try with a more recent version. Version 4.2.46 is a few years old now. dualbus@debian:~$ cat script #! /bin/bash rc_exit () { exit 0 } rc_exit dualbus@debian:~$ valgrind bash ./script ==14004== Memcheck, a memory error detector ==14004== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==14004== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==14004== Command: bash ./script ==14004== ==14004== ==14004== HEAP SUMMARY: ==14004== in use at exit: 0 bytes in 0 blocks ==14004== total heap usage: 482 allocs, 482 frees, 31,142 bytes allocated ==14004== ==14004== All heap blocks were freed -- no leaks are possible ==14004== ==14004== For counts of detected and suppressed errors, rerun with: -v ==14004== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) dualbus@debian:~$ bash --version GNU bash, version 4.4.11(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
