Re: Bash crash

Path	csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Bash crash
Date	Tue, 20 Oct 2015 09:31:02 -0400
Lines	23
Approved	bug-bash@gnu.org
Message-ID	<mailman.681.1445347877.7904.bug-bash@gnu.org> (permalink)
References	<C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se>
Reply-To	chet.ramey@case.edu
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	7bit
X-Trace	usenet.stanford.edu 1445347878 29334 208.118.235.17 (20 Oct 2015 13:31:18 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	chet.ramey@case.edu
To	Kai Wang X <kai.x.wang@ericsson.com>, "bug-bash@gnu.org" <bug-bash@gnu.org>
Envelope-to	bug-bash@gnu.org
User-Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To	<C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se>
X-Junkmail-Status	score=10/60, host=mpv5.cwru.edu
X-Junkmail-Whitelist	YES (by domain whitelist at mpv1.tis.cwru.edu)
X-detected-operating-system	by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
X-Received-From	129.22.105.36
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:11718

Show key headers only | View raw

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 Chet Ramey <chet.ramey@case.edu> - 2015-10-20 09:31 -0400

csiph-web