Bug#330122: your bash bug egrep arg list too long

2006-02-12 Thread Justin Pryzby
On Sun, Feb 12, 2006 at 02:10:46PM -0800, Kingsley G. Morse Jr. wrote: > > but I would argue that existing documentation is > > sufficient. > > This is where I must disagree. > > The error message complains about "arguments", but > the problem is with the "environment". It > inevitably misleads

Bug#330122: your bash bug egrep arg list too long

2006-02-12 Thread Kingsley G. Morse Jr.
[...] > > but I didn't see where it mentions adding the > > sizes of envp and argv. > The manpage is also in Debian, manpages-dev, and mentions it. OK. It's good to see that the sum is mentioned somewhere. [...] > $ strace -f sh ./bug.1.sh 2>&1 |grep exec |tail -1 > [pid 24558] execve("/bin/egrep

Bug#330122: your bash bug egrep arg list too long

2006-02-12 Thread Justin Pryzby
On Sun, Feb 12, 2006 at 12:25:15PM -0800, Kingsley G. Morse Jr. wrote: > On 02/12/06 11:29, Justin Pryzby wrote: > > On Sat, Feb 11, 2006 at 11:12:39AM -0800, Kingsley G. Morse Jr. wrote: > > > On 02/10/06 15:30, Justin Pryzby wrote: > > > > The problem is that ARG_MAX applies to the sum > > > > of

Bug#330122: your bash bug egrep arg list too long

2006-02-12 Thread Justin Pryzby
On Sat, Feb 11, 2006 at 11:12:39AM -0800, Kingsley G. Morse Jr. wrote: > On 02/10/06 15:30, Justin Pryzby wrote: > > The problem is that ARG_MAX applies to the sum > > of envp and argv; > > H... I didn't know that. > > If you're certain that envp is included in the Did you check the manpage e

Bug#330122: your bash bug egrep arg list too long

2006-02-11 Thread Kingsley G. Morse Jr.
On 02/10/06 15:30, Justin Pryzby wrote: > The problem is that ARG_MAX applies to the sum > of envp and argv; H... I didn't know that. If you're certain that envp is included in the sum, then shouldn't the error message reflect that it is? Thanks, Kingsley -- To UNSUBSCRIBE, email to [EMA

Bug#330122: your bash bug egrep arg list too long

2006-02-10 Thread Justin Pryzby
> On 02/09/06 12:12, Justin Pryzby wrote: > > So, I think this bug is fully understood. /bin/egrep just calls > > grep -E "$@", so if $@ is MAXARGS-1, the -E puts it over the edge. > > The error starts with "/bin/egrep" since that is the name of the > > command; if you were to mv /bin/{egrep,foo}