Re: memory leak in read builtin

2007-11-08 Thread Chet Ramey
Lars Ellenberg wrote: > Bash Version: 3.1 > Patch Level: 17 > Release Status: release > > (debian etch, bash 3.1dfsg-8) > > Description: > aparently I hit a memory leak in the read builtin. > > Repeat-By: > yes | bash -c 'ulimit -v 1000; while read a ; do :; done' > > bash: x

Re: Problem with reading file and executing other stuffs?

2007-11-08 Thread Hugh Sasse
On Thu, 8 Nov 2007, Horinius wrote: > Hugh Sasse wrote: > > Again, what problem are you trying to solve, if any? > > > I'm doing some processing in a big file which is well formatted. It's sort > of a database table (or a CVS file if you like). Every line contains a OK, if it is in fields, l

Re: bash still dies when trying to write to a tcp socket that has been closed on the other end

2007-11-08 Thread Chet Ramey
Ralf Goertz wrote: > Since nobody seemed to have noticed and the bug still exists in > >> bash --version > GNU bash, version 3.2.25(1)-release (i586-suse-linux-gnu) > Copyright (C) 2005 Free Software Foundation, Inc. > > I thought I file my report once more. Why not try setting a trap on SIGPIPE

Re: Problem with reading file and executing other stuffs?

2007-11-08 Thread Horinius
Hugh Sasse wrote: > > And vi warns about it in a similar way to ed. > > Again, what problem are you trying to solve, if any? > I'm doing some processing in a big file which is well formatted. It's sort of a database table (or a CVS file if you like). Every line contains a unique element th

bash still dies when trying to write to a tcp socket that has been closed on the other end

2007-11-08 Thread Ralf Goertz
Since nobody seemed to have noticed and the bug still exists in > bash --version GNU bash, version 3.2.25(1)-release (i586-suse-linux-gnu) Copyright (C) 2005 Free Software Foundation, Inc. I thought I file my report once more. Description: I am trying to patch bash to have it open server