[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Strange wget behavior when saving to stdout

From: Micah Cowan
Subject: Re: [Bug-wget] Strange wget behavior when saving to stdout
Date: Fri, 15 Jun 2012 20:11:53 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

On 06/15/2012 07:59 PM, Micah Cowan wrote:
> The close_stdout() thing from closeout.c is from gnulib. I'm going to
> leave it to the you, Giuseppe, to find out what's going on beyond
> that... IIRC, gnulib offers facilities for excluding certain modules, so
> that might be in order here... if it turns out to be gnulib's fault and
> not wget (which would be my strong suspicion), you may wish to report it
> to them as well. I don't know whether wget does something like closing
> stdout early or some such, but I'd certainly take a dim view to helper
> utility libraries fucking up my program exit - especially in such a
> relatively hard-to-debug fashion.

Well, it looks like we explicitly request it in
$top_srcdir/bootstrap.conf, in which case I suppose we're getting what
we deserve. Not sure I know what's the intent of this module - perhaps
to ensure that everything flushed out properly, and we report an error
in that case. I suppose if closeout is really something that's wanted,
we should take whatever pains to ensure we don't close stdout ourselves,
first (alternatively, perhaps gnulib should ignore certain types of
errors, if possible). Anyhoo...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]