On 2013-04-24 16:21, Christian Franke wrote:
The attached patch would actually fix the issue. Likely not the correct
way to do this as va_arg(param, long) is also used for the other integer
options.
Is this possibly an upstream bug which is hidden on Linux et al. due to
a different x64 ABI (whic
On Apr 24 21:40, Christian Franke wrote:
> Corinna Vinschen wrote:
> >>- DON'T forget to add casts if such Win32 API types are used with
> >>printf(). This:
> >>
> >> printf("Win32 Error=%lu\n", GetLastError());
> >>
> >>worked for all i686 and Windows x86_64, but fails now on Cygwin x86_64.
> >I
On Wed, Apr 24, 2013 at 2:21 PM, Christian Franke
wrote:
>>>
>>> Yes, option is possibly set as int (bool) but retrieved as long:
>
>
> Is this possibly an upstream bug which is hidden on Linux et al. due to a
> different x64 ABI (which requires register parameter zero extension) ?
Very possible
Christian Franke wrote:
Corinna Vinschen wrote:
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 inte
Corinna Vinschen wrote:
- DON'T forget to add casts if such Win32 API types are used with
printf(). This:
printf("Win32 Error=%lu\n", GetLastError());
worked for all i686 and Windows x86_64, but fails now on Cygwin x86_64.
I skipped that because the FAQ entry is not exactly what I wrote in
On Apr 24 20:37, Erwin Waterlander wrote:
> Op 24-4-2013 20:30, Corinna Vinschen schreef:
> >On Apr 24 20:25, Erwin Waterlander wrote:
> >>Op 24-4-2013 15:47, Corinna Vinschen schreef:
> >>> Cygwin Windows Cygwin
> >>>Linuxx86_64 Linux
> >>>Windows
Op 24-4-2013 20:30, Corinna Vinschen schreef:
On Apr 24 20:25, Erwin Waterlander wrote:
Op 24-4-2013 15:47, Corinna Vinschen schreef:
On Apr 24 14:59, Corinna Vinschen wrote:
On Apr 23 23:56, Christian Franke wrote:
Possibly a __builtin_va_list related gcc bug.
This is rather unlikely. That
On Apr 24 20:25, Erwin Waterlander wrote:
> Op 24-4-2013 15:47, Corinna Vinschen schreef:
> >On Apr 24 14:59, Corinna Vinschen wrote:
> >>On Apr 23 23:56, Christian Franke wrote:
> >>>Possibly a __builtin_va_list related gcc bug.
> >>This is rather unlikely. That code is shared between Cygwin and
Op 24-4-2013 15:47, Corinna Vinschen schreef:
On Apr 24 14:59, Corinna Vinschen wrote:
On Apr 23 23:56, Christian Franke wrote:
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 fou
On Apr 24 18:10, Christian Franke wrote:
> Corinna Vinschen wrote:
> >For clearness I decided to add a quick lecture. Hope that's ok.
>
> Makes much sense. I would suggest two additions:
>
> >...
> >- DON'T mix up int and long in printf/scanf. This:
> >
> > int i; long l;
> > printf ("%
Corinna Vinschen wrote:
For clearness I decided to add a quick lecture. Hope that's ok.
Makes much sense. I would suggest two additions:
...
- DON'T mix up int and long in printf/scanf. This:
int i; long l;
printf ("%d %ld\n", l, i);
may not print what you think it should.
On Apr 24 10:09, Christopher Faylor wrote:
> Maybe the below email should be a FAQ reference?
That's a good idea, I guess. I'll prepare such a faq entry.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT
Maybe the below email should be a FAQ reference?
cgf
On Wed, Apr 24, 2013 at 03:47:49PM +0200, Corinna Vinschen wrote:
>On Apr 24 14:59, Corinna Vinschen wrote:
>> On Apr 23 23:56, Christian Franke wrote:
>> > Possibly a __builtin_va_list related gcc bug.
>>
>> This is rather unlikely. That cod
On Apr 24 14:59, Corinna Vinschen wrote:
> On Apr 23 23:56, Christian Franke wrote:
> > 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 iss
Corinna Vinschen wrote:
> 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
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?
>
> Unlikel
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
17 matches
Mail list logo
