Package: bash
Version: 5.2.37-2+b10
Severity: important
Dear Maintainer,
I discovered this bug while utilising a bash string variable as memory load to
investigate a suspected memory issue in another application.
I then tried to reproduce this bug and had success with the following command
line:
$ TESTVAR="A"; for I in {1..32}; do TESTVAR+="$TESTVAR"; done
Segmentation fault
Cheers,
Wolf
-- System Information:
Debian Release: 13.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 7.1.3+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bash depends on:
ii base-files 13.8+deb13u7
ii debianutils 5.23.2
ii libc6 2.41-12+deb13u4
ii libtinfo6 6.5+20250216-2
Versions of packages bash recommends:
ii bash-completion 1:2.16.0-7
Versions of packages bash suggests:
pn bash-doc <none>
-- no debconf information
Thank you for using reportbug
