Henning Bekel 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
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 is the configuration i use now (derived from the archlinux
pkgbuild):
./configure --prefix=/usr --with-curses --e
