-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mark Hobley on 12/30/2009 2:56 PM:
>
> --- On Tue, 29/12/09, Eric Blake wrote:
>
>> From: Eric Blake
>> Subject: Re: Redirecting to a stream number held in a variable
>
>> You'll have to de
--- On Tue, 29/12/09, Eric Blake wrote:
> From: Eric Blake
> Subject: Re: Redirecting to a stream number held in a variable
> You'll have to demonstrate an instance of the bug in
> context, first.
Here is what I have so far:
In an empty directory create a configure.a
Eric Blake byu.net> writes:
> Can you enable shell tracing, or even a debug echo statement at the top of
> as_fn_error, in order to sniff out if someone is ever invoking that
> function with incorrect arguments?
I see one possibility - perhaps you have an error in your configure.ac script.
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mark Hobley on 12/30/2009 1:03 AM:
>> You'll have to demonstrate an instance of the bug in
>> context, first.
>
> I'm trying. I need some faulty code that consistently trips the logger. I
> don't know what causes this yet, but I have see
>$as_echo "$as_me:${as_lineno-$LINENUM}: error: $1" >&$3
That is valid, if and only if $3 expands to an integer.
> > Which shells, and what is the text of the error?
> echo "foobar" >&$3
What is $3 during the time of your testing? In isolation,
I can reproduce failures, but only when $3 is
