On 3/26/11 3:56 PM, Andreas Schwab wrote:
> Henning Bekel <h.be...@googlemail.com> writes:
>
>> I've noticed that this problem does no longer occur if bash 4.2.8 is
>> configured --with-bash-malloc. On my distribution (arch) bash is
>> configured --without-bash-malloc by default.
>
> This may indicate that bash is calling malloc in a signal handler.
Yep, that's most likely the case. Should be an easy fix.
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/
