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


Groups > gnu.bash.bug > #12044

Re: Bash crash

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: Bash crash
Date 2015-12-16 20:02 -0500
Organization ITS, Case Western Reserve University
Message-ID <mailman.58.1450314137.843.bug-bash@gnu.org> (permalink)
References <C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se> <56264216.2060606@case.edu> <CAP=cN8mxKcB8zSA6CtOwNXm95SCf9RuY0dSjEnSBwXm=+r9rtg@mail.gmail.com>

Show all headers | View raw


On 12/14/15 2:52 AM, Piotr Grzybowski wrote:
> 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

I think the likely cause is that sbrk() either has a bug or is not
emulated well.  I think what I said in

http://lists.gnu.org/archive/html/bug-bash/2015-10/msg00171.html

holds true.  The likely reason that the system malloc works is that
it doesn't use sbrk().

-- 
``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 Chet Ramey <chet.ramey@case.edu> - 2015-12-16 20:02 -0500

csiph-web