On 12/14/15 2:52 AM, Piotr Grzybowski wrote: > 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
I think the likely cause is that sbrk() either has a bug or is not emulated well. I think what I said in http://lists.gnu.org/archive/html/bug-bash/2015-10/msg00171.html holds true. The likely reason that the system malloc works is that it doesn't use sbrk(). -- ``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/
