Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
assuming a new user identity via su, thereby starting a new
interactive bash session, and entering the first command
* What was the outcome of this action?
bash bails with
malloc: unknown:0: assertion botched
malloc: block on free list clobbered
last command: exit
Aborting...
leaving the terminal misconfigured in the process as well; note
that there was no exit command given at all - bash made that up
* What outcome did you expect instead?
an interactive bash session that lives beyond the first command (line)
*** End of the template - remove these template lines ***