I'm still seeing this exact same crash with bash_4.3-7ubuntu1. In fact,
I also see it with a bash binary built from the upstream git (bash 4.3
patch 18).
This is the stack trace I'm getting:
codewiz@xyzzy:~$
malloc: unknown:0: assertion botched
free: called with unallocated block argument
Confirming that the bash binary from the trace *does* include patches 9 through
11.
Now trying to get a better trace from a binary compiled with -g
Please reopen this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package bash - 4.3-7ubuntu1
---
bash (4.3-7ubuntu1) trusty-proposed; urgency=medium
* Merge with Debian, replacing local with upstream patches. LP:
#1294669.
bash (4.3-7) unstable; urgency=medium
* Apply upstream patches 009 - 011 (replacing local
This bug was fixed in the package bash - 4.3-7ubuntu1
---
bash (4.3-7ubuntu1) trusty-proposed; urgency=medium
* Merge with Debian, replacing local with upstream patches. LP:
#1294669.
bash (4.3-7) unstable; urgency=medium
* Apply upstream patches 009 - 011 (replacing local
Tested with bash 4.3-7ubuntu1, and I can't reproduce the issue now,
hence fixed for me. Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bash from trusty-proposed fixed the issue for me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage notifications about
The trusty-proposed patch works for me, too.
Testcase:
1. Fresh install of 32bit Ubuntu 14.04
Before the patch:
$ bash
$ echo $BASH_VERSION
4.3.8(1)-release
$ ls
$ !
$ ENTER
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last
The crash takes some time to reproduce on my laptop, so I attached gdb
to an interactive bash process and got this stacktrace when it finally
crashed:
Program received signal SIGABRT, Aborted.
0x7761df79 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56
Am 22.04.2014 00:54, schrieb Brian Murray:
There appears to already be an upload fixing this in the unapproved
queue for Trusty proposed. The bug report is just missing SRU
information - test case, etc.
the test case always was in the bug report. the bug number #1294669 is mentioned
in
Hello Colin, or anyone else affected,
Accepted bash into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/bash/4.3-7ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: bash i386
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage notifications about this bug go to:
This bug can be reproduced in both amd64 and ia386 Ubuntu 14.04 release
versions.
1. Boot to Live Ubuntu
2. Open a Terminal
3. Enter the following commands:
$ bash
$ ls
$ !
$ ENTER
Result is a crashed bash as described above:
malloc: /usr/homes/chet/src/bash/src/parse.y:2314:
Core dump generated by bash after a fresh 32bit Desktop installation of Ubuntu
14.04 LTS with empty home directory.
Bash ! also crashes shells on both Ubuntu Live Installer CDs 32+64 bit
siggy $ gdb /bin/bash core
GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
...
Reading symbols from /bin/bash...(no
** Also affects: bash (Ubuntu Trusty)
Importance: High
Assignee: Matthias Klose (doko)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed
Bug still exists in bash version 4.3.8(1)-release
siggy $ bash --version
GNU bash, version 4.3.8(1)-release (i686-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to
This bug can also be produced with compiled original version 4.3 retrieved from:
http://archive.ubuntu.com/ubuntu/pool/main/b/bash/bash_4.3.orig.tar.gz
bash-4.3$ ./bash
bash-4.3$ echo $BASH_VERSION
4.3.0(1)-release
bash-4.3$ ls
bash-4.3$ !
bash-4.3$
malloc:
There appears to already be an upload fixing this in the unapproved
queue for Trusty proposed. The bug report is just missing SRU
information - test case, etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah sorry for the long paste ... Backtrace is in the attached file.
** Attachment added: crash
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1294669/+attachment/4085733/+files/crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/bin/bash crashes everytime calling q! followed by sudo su
Bash crashed during the following sequence:
user@LINUXPC:~$ q!
q!: command not found
user@LINUXPC:~$ sudo su
malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last command: q!
** Changed in: bash (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage
** Changed in: bash (Ubuntu)
Milestone: None = trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage
The test case still causes a crash with bash version 4.3-6ubuntu1.
** Changed in: bash (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
** Branch linked: lp:ubuntu/trusty-proposed/bash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage notifications about this
This bug was fixed in the package bash - 4.3-4ubuntu2
---
bash (4.3-4ubuntu2) trusty; urgency=medium
* Fix a display issue when a multiline command is aborted with ^C.
* Fix a crash after a failed history expansion. LP: #1294669.
-- Matthias Klose d...@ubuntu.com Fri, 28 Mar
I was able to recreate this crash by performing the following:
bdmurray@blacklightning:~$ x!
x!: command not found
bdmurray@blacklightning:~$ x!
malloc: .././parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last command: x!
Aborting...Aborted (core dumped)
--
You
For further details see the duplicates of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage notifications about this
Yes, that's a reproducer for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294669
Title:
bash crashed with SIGABRT in programming_error()
To manage notifications about this bug go to:
so it appears the ! token is the culprit at a guess:
ps = {parser_state = 524288, token_state = 0x1629768, token = 0x11f4008 !,
token_buffer_size = 1520, input_line_terminator = 0, eof_encountered = 0,
prompt_string_pointer = 0x6fc920 ps1_prompt, current_command_line_count = 0,
I did a clean install of Trusty yesterday and I will keep track to see
if this issue occurs again. It seemed to happen only when I had been
very busy in bash and had done a bunch of cursor-up repeated commands
and somehow it just died under me.
--
You received this bug notification because you
lowering importance to high, and making the bug report public. would be
good to know if somebody else can reproduce this.
** Information type changed from Private to Public
** Changed in: bash (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a
30 matches
Mail list logo
