Re: va_list and x86_64 possible bug (?)

2007-10-17 Thread Macy Gasp
On 10/17/07, Andrew Haley <[EMAIL PROTECTED]> wrote: > Macy Gasp writes: > > On 10/17/07, Macy Gasp <[EMAIL PROTECTED]> wrote: > > > On 10/17/07, Andrew Haley <[EMAIL PROTECTED]> wrote: > > > > Macy Gasp writes: > > >

Re: va_list and x86_64 possible bug (?)

2007-10-17 Thread Macy Gasp
On 10/17/07, Macy Gasp <[EMAIL PROTECTED]> wrote: > On 10/17/07, Andrew Haley <[EMAIL PROTECTED]> wrote: > > Macy Gasp writes: > > > Hi everybody, > > > > Read the Fine Manual: > > > > > >int vsprintf(char *str, const cha

Re: va_list and x86_64 possible bug (?)

2007-10-17 Thread Macy Gasp
On 10/17/07, Andrew Haley <[EMAIL PROTECTED]> wrote: > Macy Gasp writes: > > Hi everybody, > > Read the Fine Manual: > > >int vsprintf(char *str, const char *format, va_list ap); > >The functions vprintf(), vfprintf(), vsprintf(), vsnpri

va_list and x86_64 possible bug (?)

2007-10-17 Thread Macy Gasp
Hi everybody, I'm experiencing a weird behaviour when using va_list with gcc 4.1.2 on a x86_64 linux distribution. Below is my test program (yes, I know about the possible buffer overflows but please, bear with me, this is just a proof of concept): #include #include int var(const char* fmt, .