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. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
