This is the mail archive of the
mailing list for the Cygwin project.
Re: Difference in 32/64-bit curl.
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 24 Apr 2013 14:59:30 +0200
- Subject: Re: Difference in 32/64-bit curl.
- References: <51766C22 dot 10702 at bahnhof dot se> <51770372 dot 4070408 at t-online dot de>
- Reply-to: cygwin at cygwin dot com
On Apr 23 23:56, Christian Franke wrote:
> Fredrik Rothamel wrote:
> >I just noticed that in 64-bit cygwin curl always include the
> >http-headers in the response.
> >(Old behaviour is to only include headers when -i option is specified)
> >Is this an intentional change?
> Unlikely. In this case it should be possible to revert the default
> -i (--include) with --no-include.
> According to a quick gdb session using curl-debug package the
> corresponding variable config->include_headers is not set during
> option processing. But later in Curl_setopt(., CURLOPT_HEADER, .)
> the variable data->set.include_header is set true because some
> va_arg(param, long) is nonzero.
> Possibly a __builtin_va_list related gcc bug.
This is rather unlikely. That code is shared between Cygwin and
Mingw, and chances are that the bug would have been found already.
What about a type issue? int vs. long?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple