Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #12008

Re: Bash crash

Path csiph.com!au2pb.net!feeder.erje.net!2.us.feeder.erje.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From Piotr Grzybowski <narsil.pl@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Bash crash
Date Mon, 14 Dec 2015 08:52:56 +0100
Lines 43
Approved bug-bash@gnu.org
Message-ID <mailman.2065.1450079580.31583.bug-bash@gnu.org> (permalink)
References <C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se> <56264216.2060606@case.edu>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8
X-Trace usenet.stanford.edu 1450079581 31445 208.118.235.17 (14 Dec 2015 07:53:01 GMT)
X-Complaints-To action@cs.stanford.edu
Cc Kai Wang X <kai.x.wang@ericsson.com>, "bug-bash@gnu.org" <bug-bash@gnu.org>
To Chester Ramey <chet.ramey@case.edu>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F8BNSTXLaQdE3+jX+R0irSduZsaMQELtyBDffwX+w9I=; b=m+mVuc1lPw2IxenFZBGNeomUeC6x7nL1W4vfnpu0Pcdngbs8KW/2rd2266KIt/TOHR M49uz7HnGZW92jax0L/KaOww7Xw/iqUKB1PhoJcNB/FbnfpIUavJuset13Xr9yUG91NB ChULpn2ebEpqJM80beGtN+YPl5KSjnopLAUq74ODbxYwoyQXML24ELOJKIeVEghuRZSF pXm+n4IvIz5F6BwOCl+Ba0BkHBEWFSQooDGa30pr9MeG8FbvqNcs9Ebj47OK6KTg2bf3 mdHuaDSyLyb3gx20F58PfpWss4Ylg0ivdw4BXnbJTlppNGCo3h48pzpLOHonvb9Nm1HF w05g==
X-Received by 10.112.173.202 with SMTP id bm10mr12721223lbc.56.1450079576224; Sun, 13 Dec 2015 23:52:56 -0800 (PST)
In-Reply-To <56264216.2060606@case.edu>
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From 2a00:1450:4010:c04::22f
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.14
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:12008

Show key headers only | View raw


Hey,

 we have had an off--list discussion with Kai on this (to shorten the
30 mails we exchanged ;-) I am writing this summary). He solved the
issue by --without-bash-malloc which could indicate a bug or lack of
proper support in lib/malloc/malloc.c for his platform. However, we
were unable to get more information, it is not that easy to reproduce.
If there is no one who can reproduce this we can try again, if you
think it is worthwhile.
 For now, if anyone bumps into this, try, according to Kai findings,
configure with --without-bash-malloc

cheers,
pg




On Tue, Oct 20, 2015 at 3:31 PM, Chet Ramey <chet.ramey@case.edu> wrote:
> On 10/19/15 10:47 PM, Kai Wang X wrote:
>> Dear,
>>
>>
>>
>> We have two products which are using bash 4.2 and 4.3 separately. They all
>> meet bash crash issue. Please refer to the attached files.
>>
>> It is hard for me to understand the bash source code to find the root cause
>> out.
>
> It really looks like sbrk(2) is failing here, but since I don't have
> any way to reproduce it, that may not be it.  This could be caused by
> your process exceeding its memory resource limit or your system's swap
> space being exhausted.
>
> Chet
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/
>

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: Bash crash Piotr Grzybowski <narsil.pl@gmail.com> - 2015-12-14 08:52 +0100

csiph-web