*** This bug is a duplicate of bug 1294669 ***
https://bugs.launchpad.net/bugs/1294669
This sequence of commands consistently ends in that crash:
root@tribble:~# !
root@tribble:~# lshw
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk
*** This bug is a duplicate of bug 1294669 ***
https://bugs.launchpad.net/bugs/1294669
It isn't sufficient as the retracers need a specifically formatted bug
to retrace the crash. I've created one in bug 1298522.
** This bug has been marked a duplicate of private bug 1298522
--
You
*** This bug is a duplicate of bug 1294669 ***
https://bugs.launchpad.net/bugs/1294669
** This bug is no longer a duplicate of bug 1298522
bash crashed with SIGABRT in programming_error()
** This bug has been marked a duplicate of bug 1294669
bash crashed with SIGABRT in
I received a core dump when trying to recreate this bug. The crash
should result in a .crash file in /var/crash/ and then an apport dialog
offering to file the bug. It'd be great if you could submit the
automatic crash report for this and then we can mark this bug as a
duplicate of that one.
** Attachment added: Crash report
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1295467/+attachment/4043616/+files/bash.crash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295467
The affected boxes are headless servers, on networks without outbound
HTTP(S) access. Is the attached upload of the crash report sufficient?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295467
