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
cheers, pg On Tue, Oct 20, 2015 at 3:31 PM, Chet Ramey <chet.ra...@case.edu> wrote: > 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 c...@case.edu http://cnswww.cns.cwru.edu/~chet/ >
