Your message dated Wed, 5 Jun 2024 08:48:51 +0200
with message-id <[email protected]>
and subject line Re: bash wants to be vi when it grows up .. q! crashes bash
has caused the Debian Bug report #749270,
regarding bash wants to be vi when it grows up .. q! crashes bash
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.)
--
749270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 4.3-7
Severity: normal
joey@wren:~/tmp/ghc-7.6.3>q!
-bash: q!: command not found
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
Aborting...Connection to kite closed.
This seems reproducible, at least in my bash setup, and on this particular i386
system. I could not reproduce it on an amd64 system with identical bash configs.
In a fresh user account with no bashrc, I also reproduced it, although slightly
differently. After the q! command, hitting enter a second time crashes it.
foo@wren:/home/joey$ q!
bash: q!: command not found
foo@wren:/home/joey$
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last command: q!
Aborting...- exit 134
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 5.2.21-2+b1
On Sun, 25 May 2014 15:25:08 -0400 Joey Hess <[email protected]> wrote:
Package: bash
Version: 4.3-7
Severity: normal
joey@wren:~/tmp/ghc-7.6.3>q!
-bash: q!: command not found
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
Aborting...Connection to kite closed.
This seems reproducible, at least in my bash setup, and on this particular i386
system. I could not reproduce it on an amd64 system with identical bash configs.
In a fresh user account with no bashrc, I also reproduced it, although slightly
differently. After the q! command, hitting enter a second time crashes it.
foo@wren:/home/joey$ q!
bash: q!: command not found
foo@wren:/home/joey$
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last command: q!
Aborting...- exit 134
Hi,
this no longer seems to be reproducible on a i386 VM with bash
5.2.21-2+b1. Maybe bash now wants to become emacs?
Regards,
--
Gioele Barabucci
--- End Message ---
