On Tue, Jun 15, 2021 at 04:20:22PM -0400, Chet Ramey wrote:
> It depends on the libc implementation of setlocale(3).
>
> This has come up a number of times before:
>
> https://lists.gnu.org/archive/html/bug-bash/2015-07/msg00073.html
> https://lists.gnu.org/archive/html/bug-bash/2017-04/msg00063.
I'm glad to see the issue is not widespread, for sure!
I'm running fully updated Pop! OS 20.04 (debian based), which also has an older
version of bash (installed natively).
Bash Version: 5.0Patch Level: 17Release Status: release
Hopefully the issue has already been fixed, and the `apt` packages
On 6/15/21 3:19 PM, Zachary Fields wrote:
Again, this can be reproduced with only Valgrind and Bash installed, by
copy/pasting the following command:
Don't be so sure:
==34794== LEAK SUMMARY:
==34794==definitely lost: 0 bytes in 0 blocks
==34794==indirectly lost: 0 bytes in 0 blocks
==
Again, this can be reproduced with only Valgrind and Bash installed, by
copy/pasting the following command:
echo "#! /bin/bashecho 'Am I leaking?'" > leak.sh \&& chmod +x leak.sh \&&
LC_ALL=C valgrind -v --leak-check=full /bin/bash leak.sh
This is the best log I know how to generate using Valg
On 6/12/21 12:16 PM, Zachary Fields via Bug reports for the GNU Bourne
Again SHell wrote:
LEAK SUMMARY: ==1365336== definitely lost: 12 bytes in 1 blocks ==1365336==
How about more details fromn valgrind about where it thinks the leak is?
--
``The lyf so short, the craft
Configuration Information [Automatically generated, do not change]:Machine:
x86_64OS: linux-gnuCompiler: gccCompilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-SmNvvg/bash-5.0=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -Wno-parentheses
-Wno-format-securityuname outp
