https://bugzilla.novell.com/show_bug.cgi?id=330615 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c17 --- Comment #17 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2007-12-16 12:08:18 MST --- And one more note: http://www.gnu.org/software/libc/manual/html_node/Variable-Arguments-Output.... says " In some other systems, the va_list pointer may become invalid after the call to vprintf, so you must not use va_arg after you call vprintf. Instead, you should call va_end to retire the pointer from service. However, you can safely call va_start on another pointer variable and begin fetching the arguments again through that pointer. Calling vprintf does not destroy the argument list of your function, merely the particular pointer that you passed to it. GNU C does not have such restrictions. You can safely continue to fetch arguments from a va_list pointer after passing it to vprintf, and va_end is a no-op. (Note, however, that subsequent va_arg calls will fetch the same arguments which vprintf previously used.) " That suggests that the crash shouldn't happen with gcc but it still does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.