Hi,
Indeed, you're absolutely right. Reminder to myself: always test
latest devel version before reporting bugs :)
I've compiled devel with "make DEBUG= MALLOC_DEBUG=" and I could not
reproduce the issue with either of the commands.
Thanks a lot! :)
egmont
On Sun, Sep 24, 2017 at 7:48 PM, Che
On 9/23/17 4:55 PM, Egmont Koblinger wrote:
> Is there anything bash could do to prevent incorrect behavior of its
> built-in commands when a SIGWINCH is encountered? And of course I
> don't mean the "echo" command only.
You can try, as the bash devel branch does, to install the SIGWINCH
signal h
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
