Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Aharon Robbins <arnold@skeeve.com>
Newsgroups: gnu.bash.bug
Subject: Re: Bash crash
Date: Wed, 21 Oct 2015 20:51:06 +0300
Lines: 64
Approved: bug-bash@gnu.org
Message-ID: <mailman.742.1445449884.7904.bug-bash@gnu.org>
References: <C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se> <56264216.2060606@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: TEXT/PLAIN
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Trace: usenet.stanford.edu 1445449884 18835 208.118.235.17 (21 Oct 2015 17:51:24 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org
To: kai.x.wang@ericsson.com
Envelope-to: bug-bash@gnu.org
In-reply-to: <mailman.718.1445394604.7904.bug-bash@gnu.org>
X-Newsgroups: gnu.bash.bug
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 194.90.9.21
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:11734

Sounds like a hardware problem with the RAM on your system....

HTH,

Arnold

In article <mailman.718.1445394604.7904.bug-bash@gnu.org> you write:
>Hi Chet,
>
>Thank you for your response.
>
>But it does not make sense since sbrk failure will be checked:
>
>  mp =3D (union mhead *) sbrk (sbrk_amt);
>
>  /* Totally out of memory. */
>  if ((long)mp =3D=3D -1)
>    goto morecore_done;
>
>The script just runs when my equipment boots up. Also it is hard to
>reproduce in my environment. Only every few times of my equipment
>booting up, it generates a coredump file.
>
>-----Original Message-----
>From: Chet Ramey [mailto:chet.ramey@case.edu]=20
>Sent: 2015=E5=B9=B410=E6=9C=8820=E6=97=A5 21:31
>To: Kai Wang X; bug-bash@gnu.org
>Cc: chet.ramey@case.edu
>Subject: Re: Bash crash
>
>On 10/19/15 10:47 PM, Kai Wang X wrote:
>> Dear,
>>=20
>> =20
>>=20
>> We have two products which are using bash 4.2 and 4.3 separately. =
They=20
>> all meet bash crash issue. Please refer to the attached files.
>>=20
>> It is hard for me to understand the bash source code to find the r=
oot=20
>> 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 yo=
ur
>process exceeding its memory resource limit or your system's swap sp=
ace
>being exhausted.
>
>Chet
>
>--
>``The lyf so short, the craft so long to lerne.'' - Chaucer
>=09=09 ``Ars longa, vita brevis'' - Hippocrates
>Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu=
/~chet/


--=20
Aharon (Arnold) Robbins =09=09arnold AT skeeve DOT com