public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/366] Compiling on 64-bit yields segmentation fault when run, on 32-bit runs fine. Date: Fri, 03 Sep 2004 04:23:00 -0000 [thread overview] Message-ID: <20040903042320.16526.qmail@sourceware.org> (raw) In-Reply-To: <20040903023911.366.dafrabbit@yahoo.com> ------- Additional Comments From aj at suse dot de 2004-09-03 04:23 ------- The ISO C99 standard in section 7.15 #3 forbids to usages of va_list without a va_end/va_start. Removing one vfprintf call from io_vprint fixes the problem. Your program is not valid C, it just works by chance on 32-bit. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://sources.redhat.com/bugzilla/show_bug.cgi?id=366 ------- 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:[~2004-09-03 4:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-03 2:39 [Bug libc/366] New: " dafrabbit at yahoo dot com 2004-09-03 2:39 ` [Bug libc/366] " dafrabbit at yahoo dot com 2004-09-03 4:23 ` aj at suse dot de [this message] 2004-09-03 7:41 ` jakub at redhat dot com 2004-09-03 13:01 ` dafrabbit at yahoo 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=20040903042320.16526.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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).