Re: double free corruption bash 4.2.53(1)-release

Oddly enough it seems to have resolved itself after my libc recompile with debug symbols. ifrit ~ # echo $BASH_VERSION 4.3.48(1)-release Before the libc recompile with debug symbols regardless of locale, the printf builtin was just printing "\u200b\n" as "\u200B" The problem seems to have resol

Re: double free corruption bash 4.2.53(1)-release

Thanks for at least trying. I haven't found anyone else that has been able to replicate it either, this would be a huge pain to chase down for me. I'm able to replicate it 100% of the time on my system. So if anyone IS interested in trying please contact me and I will give them a shell account t

Re: double free corruption bash 4.2.53(1)-release

Went ahead and compiled libc and bash with debug symbols. I can't seem to trigger it when I am actually IN an interactive shell (e.g. having a pts allocated to myself), but it still triggers with the shell script. ifrit crash # gdb /bin/bash GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1 Copyright (C) 20

double free corruption bash 4.2.53(1)-release

Hi all, I found a bug in bash 4.2.48+ (doesn't seem to effect bash 4.3) : This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was