X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=voLfYRizABKHQ+GmcpH5jZiTkhyTtjrmKfOilNENhwxXkRcoLi1bg gh0AD1jx1CNvsvnKYxwYpaPwPl8R8DW7ob9QMNzv996Vsv5qf7oh69zd344YXLoF nrj2NEGOl2sZlKeIfxdy3sGezFFr5tgjQJ+nz1feuRByfj5q4fWVb8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=xpXBkEhxW+lOCnx3xYds7b7dZwI=; b=EJhUUdITiqDSePrBiZ3neo2KNsly UQc4CPMT9JXab5hDpEWZIIdBgV64Rv1ir1Wk0oqunWKD8BtqIYm5sKRFrw/1tSmA fx6lj/BATbZzxjpeFomfVlMrL6tr3DKKgQkYRjSluSz3/kyHmhzpD71I1flIhBzp x8fhnuaKSMuI4AA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Wed, 24 Apr 2013 14:59:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Difference in 32/64-bit curl. Message-ID: <20130424125930.GQ26397@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51766C22 DOT 10702 AT bahnhof DOT se> <51770372 DOT 4070408 AT t-online DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51770372.4070408@t-online.de> User-Agent: Mutt/1.5.21 (2010-09-15) On Apr 23 23:56, Christian Franke wrote: > Fredrik Rothamel wrote: > >Hi, > > > >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 -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple