va_arg only for bult-in types?

[Derek Baker]

I have this code which compiles on the MINGW version of GCC 3.4.2:

vector<string> Labels ;
va_list va_Labels;

va_start(va_Labels, Number);

for(int i= 0; i< Number; ++i)
{
Labels.push_back(va_arg(va_Labels, string));
}

va_end(va_Labels);

It compiles, but cause a segmentation fault when run. I have similar
code that extracts ints and it runs fine.

 

[Victor Bazarov]

I have this code which compiles on the MINGW version of GCC 3.4.2:

vector<string> Labels ;
va_list va_Labels;

va_start(va_Labels, Number);

for(int i= 0; i< Number; ++i)
{
Labels.push_back(va_arg(va_Labels, string));
}

va_end(va_Labels);

It compiles, but cause a segmentation fault when run. I have similar
code that extracts ints and it runs fine.

To answer the question in the subject line, yes, only for built-in types.

V

 

[Derek Baker]

I have this code which compiles on the MINGW version of GCC 3.4.2:

vector<string> Labels ;
va_list va_Labels;

va_start(va_Labels, Number);

for(int i= 0; i< Number; ++i)
{
Labels.push_back(va_arg(va_Labels, string));
}

va_end(va_Labels);

It compiles, but cause a segmentation fault when run. I have similar
code that extracts ints and it runs fine.

It is on the "Labels.push_back(va_arg(va_Labels, string));" line that
the fault occurs.

 

[Derek Baker]

To answer the question in the subject line, yes, only for built-in types.

V

Thanks Victor, it's running now with C strings.

 

[Ron Natalie]

I have this code which compiles on the MINGW version of GCC 3.4.2:

It doesn't have to be a built in type, it can be a class as long as the
class is POD.