public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "timp at pulsic dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4977] SEGV in strlen() of string argument of vsnprintf call on RHEL WS3/64-bit Date: Wed, 29 Aug 2007 15:58:00 -0000 [thread overview] Message-ID: <20070829155823.9413.qmail@sourceware.org> (raw) In-Reply-To: <20070829152853.4977.timp@pulsic.com> ------- Additional Comments From timp at pulsic dot com 2007-08-29 15:58 ------- (In reply to comment #1) > The testcase is invalid. > Please read http://www.opengroup.org/onlinepubs/009695399/basedefs/stdarg.h.html > carefully. Agh - stupidity hits. Thanks for the link - I guess this means passing the va_list as a function parameter is highly implementation specific and will potentially be unavailable on some systems (e.g. HP-UX 11i even with recent compilers has no va_copy) or with no c9x compliant compilers. > Particularly you are missing va_copy and another va_end. yep - on C99 systems. That went past a few of us, should have realised. Cheers tim -- http://sourceware.org/bugzilla/show_bug.cgi?id=4977 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2007-08-29 15:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-29 15:29 [Bug libc/4977] New: " timp at pulsic dot com 2007-08-29 15:40 ` [Bug libc/4977] " jakub at redhat dot com 2007-08-29 15:58 ` timp at pulsic dot com [this message] 2007-08-29 16:10 ` jakub at redhat dot com 2007-08-29 16:34 ` timp at pulsic dot com 2007-08-29 16:41 ` jakub at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070829155823.9413.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).