Your message dated Sat, 23 Mar 2024 12:26:11 +0100
with message-id <[email protected]>
and subject line Re: Bug#929668: bash: Valgrind reports 'definitely lost'
memory in main/set_default_locale
has caused the Debian Bug report #929668,
regarding bash: Valgrind reports 'definitely lost' memory in
main/set_default_locale
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
929668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929668
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 5.0-4
Severity: important
Dear Maintainer,
I do lot's of software development and testing with valgrind on Debian unstable.
Several testsuites of OSS projects use bash as part of the tests.
The current bash version breaks test suite due to a 'definitely lost block'.
It doesn't matter how you invoke bash. Here is just an example.
$ valgrind --leak-check=yes bash x
==2103== Memcheck, a memory error detector
==2103== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2103== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==2103== Command: bash x
==2103==
bash: x: No such file or directory
==2103==
==2103== HEAP SUMMARY:
==2103== in use at exit: 40,853 bytes in 631 blocks
==2103== total heap usage: 798 allocs, 167 frees, 60,518 bytes allocated
==2103==
==2103== 12 bytes in 1 blocks are definitely lost in loss record 80 of 220
==2103== at 0x483577F: malloc (vg_replace_malloc.c:299)
==2103== by 0x195E8D: xmalloc (in /bin/bash)
==2103== by 0x18F51A: set_default_locale (in /bin/bash)
==2103== by 0x135EE6: main (in /bin/bash)
==2103==
==2103== LEAK SUMMARY:
==2103== definitely lost: 12 bytes in 1 blocks
==2103== indirectly lost: 0 bytes in 0 blocks
==2103== possibly lost: 0 bytes in 0 blocks
==2103== still reachable: 40,841 bytes in 630 blocks
==2103== suppressed: 0 bytes in 0 blocks
==2103== Reachable blocks (those to which a pointer was found) are not shown.
==2103== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==2103==
==2103== For counts of detected and suppressed errors, rerun with: -v
==2103== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Building bash 5.0 from upstream fixes this issue for me.
Regards, Tim
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bash depends on:
ii base-files 10.3
ii debianutils 4.8.6.1
ii libc6 2.28-10
ii libtinfo6 6.1+20181013-2
Versions of packages bash recommends:
ii bash-completion 1:2.8-6
Versions of packages bash suggests:
pn bash-doc <none>
-- Configuration Files:
/etc/bash.bashrc changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.2.21-2
On Tue, 28 May 2019 10:22:33 +0200 Tim Ruehsen <[email protected]> wrote:
Package: bash
Version: 5.0-4
Severity: important
Dear Maintainer,
I do lot's of software development and testing with valgrind on Debian unstable.
Several testsuites of OSS projects use bash as part of the tests.
The current bash version breaks test suite due to a 'definitely lost block'.
It doesn't matter how you invoke bash. Here is just an example.
$ valgrind --leak-check=yes bash x
[...]
==2103== LEAK SUMMARY:
==2103== definitely lost: 12 bytes in 1 blocks
==2103== indirectly lost: 0 bytes in 0 blocks
==2103== possibly lost: 0 bytes in 0 blocks
[...]
Building bash 5.0 from upstream fixes this issue for me.
Hi,
the upstream fixes reached the Debian package: version 5.2.21-2 is not
affected by this bug.
$ valgrind --leak-check=yes bash x
[...]
==1902250== LEAK SUMMARY:
==1902250== definitely lost: 0 bytes in 0 blocks
==1902250== indirectly lost: 0 bytes in 0 blocks
==1902250== possibly lost: 0 bytes in 0 blocks
Regards,
--
Gioele Barabucci
--- End Message ---
