Path: csiph.com!xmission!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: Thu, 22 Oct 2015 19:07:44 +0200
Lines: 93
Approved: bug-bash@gnu.org
Message-ID: <mailman.820.1445533669.7904.bug-bash@gnu.org>
References: <C2FB93DF99E5FD43B0413EDB326AE2AA2B942E8F@ESGSCMB107.ericsson.se> <56264216.2060606@case.edu> <C2FB93DF99E5FD43B0413EDB326AE2AA2B94421D@ESGSCMB107.ericsson.se> <CAP=cN8n2FKQB+OcB-VWtCcm9A-z5VueUA0XS0F3DgEE3iobUQw@mail.gmail.com> <C2FB93DF99E5FD43B0413EDB326AE2AA2B9445C1@ESGSCMB107.ericsson.se>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Aharon Robbins <arnold@skeeve.com>, "bug-bash@gnu.org" <bug-bash@gnu.org>, "chet.ramey@case.edu" <chet.ramey@case.edu>
To: Kai Wang X <kai.x.wang@ericsson.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <C2FB93DF99E5FD43B0413EDB326AE2AA2B9445C1@ESGSCMB107.ericsson.se>
Precedence: list
Xref: csiph.com gnu.bash.bug:11747

 do I understand correctly, that when you comment the line 187 the
issue is not existent?

cheers,
pg


On Thu, Oct 22, 2015 at 4:39 AM, Kai Wang X <kai.x.wang@ericsson.com> wrote=
:
> Hi all,
>
> Thank you all!
>
> The issue happens since we added a new process launched by a bash script.=
 Before that, no "sbrk issues" were found and hundreds of process including=
 scripts were running in my equipment. So it is hard for me to believe that=
 there are RAM or sbrk issues already exist on my system. Also bash is used=
 by more users world-wide, so ... I am being confused...
>
> The process named "com" launched by script command "com.sh start". Pls re=
fer to the attached files. It looks easy, doesn't it?
>
> @Piotr,
>
> Sure. Every equipment has the possibility of the issue.
>
>
> -----Original Message-----
> From: Piotr Grzybowski [mailto:narsil.pl@gmail.com]
> Sent: 2015=E5=B9=B410=E6=9C=8821=E6=97=A5 19:27
> To: Kai Wang X
> Subject: Re: Bash crash
>
> hello,
>
>  does the problem also appear on other pieces of equipment? I mean, diffe=
rent phisical machine, of the same sort?
>
> pg
>
>
>
>
>
> On Wed, Oct 21, 2015 at 4:29 AM, Kai Wang X <kai.x.wang@ericsson.com> wro=
te:
>> 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 repr=
oduce in my environment. Only every few times of my equipment booting up, i=
t generates a coredump file.
>>
>> -----Original Message-----
>> From: Chet Ramey [mailto:chet.ramey@case.edu]
>> 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,
>>>
>>>
>>>
>>> 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 pro=
cess 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/~ch=
et/