FWIW, I spun up a new Debian VM with KDE running on Wayland, and can't reproduce with OP's .bashrc in Konsole.
Debian 12.12 bash 5.2.15-2+b9 libc6 2.36-9+deb12u13 Since OP's prompt is fiddling with the history, I wonder if they still see the behavior starting with a new .bash_history? Err, as I typed that, I went to double-check that PS1 was set to what they indicated, and though I could not reproduce it when entering "$(;" (w/o quotes), it did crash when I did "echo $PS1": [image: image.png] On Mon, Oct 20, 2025 at 2:56 PM Chet Ramey <[email protected]> wrote: > On 10/17/25 5:31 PM, Grisha Levit wrote: > > > > On 10/17/25 2:01 AM, Casey Connor wrote: > > > > > > > Bash Version: 5.2 > > > > Patch Level: 15 > > > > Release Status: release > > > > > > > > Description: > > > > > > > > If I open a new terminal and enter the (obviously malformed) command > > > > "$(;" (without quotes) I get a bash crash about 90% of the time. > > > > > > Thanks for the report. I can't reproduce this using bash-5.3 on RHEL. > I > > > don't have a Debian system handy to test on. > > > > > > > I can reproduce this on Debian 12 but only if bash is started exactly as > > OP describes, with the specified contents in ~/.bashrc, not e.g. using > > --rcfile /tmp/op.bashrc. > > Can you see anything with valgrind? I can't reproduce it with bash-5.3 on > Debian 12.12, even when starting bash with that ~/.bashrc. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/ >
