Re: memory leak in read builtin

Chet Ramey <[EMAIL PROTECTED]> writes: > That code is quite different in bash-3.2, and the memory leak is gone. Definitely neither. --- builtins/read.def |9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) Index: builtins/read.def =

Re: memory leak in read builtin

Chet Ramey <[EMAIL PROTECTED]> writes: > Chet Ramey wrote: >> Andreas Schwab wrote: >> >>> I can still reproduce it with 3.2.25, where the code is identical. >> >> Really? I let the loop run for 45 minutes last night before killing it, >> without a memory allocation error. I'll check again. >

Re: memory leak in read builtin

Chet Ramey wrote: > Andreas Schwab wrote: > >> I can still reproduce it with 3.2.25, where the code is identical. > > Really? I let the loop run for 45 minutes last night before killing it, > without a memory allocation error. I'll check again. And today it ran for more than an hour. I'm not

Re: bash's fallback implementation of vsnprintf(3) is nonconformant and breaks printf(1)

Rich Felker wrote: > bash-3.2.0(1)-release built on a system without native asprintf: > $ printf %x\\n 0x8000 > -8000 Patch 9 to bash-3.2 fixed this. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, IT

Re: memory leak in read builtin

Andreas Schwab wrote: > I can still reproduce it with 3.2.25, where the code is identical. Really? I let the loop run for 45 minutes last night before killing it, without a memory allocation error. I'll check again. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

bash's fallback implementation of vsnprintf(3) is nonconformant and breaks printf(1)

bash-3.2.0(1)-release built on a system without native asprintf: $ printf %x\\n 0x8000 -8000 %x is an unsigned format specifier; printing it as signed is bogus. I tracked the problem down to the implementation of vsnprintf_internal which bash uses to implement asprintf if it's not present.

Re: memory leak in read builtin

Chet Ramey <[EMAIL PROTECTED]> writes: > That code is quite different in bash-3.2, and the memory leak is gone. I can still reproduce it with 3.2.25, where the code is identical. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg,

$RANDOM incorrectly seeded in subshells

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACKA