Re: Bash crash

[Aharon Robbins]

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 = (union mhead *) sbrk (sbrk_amt);
>
>  /* Totally out of memory. */
>  if ((long)mp == -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] 
>Sent: 2015年10月20日 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
>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/


-- 
Aharon (Arnold) Robbins                 arnold AT skeeve DOT com