public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/14250] ia64 makecontext.c writes to stderr and it should not. Date: Mon, 18 Jun 2012 14:19:00 -0000 [thread overview] Message-ID: <bug-14250-131-diThmPSpfb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14250-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14250 --- Comment #2 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-06-18 14:19:07 UTC --- Mike, I didn't notice the call to exit(). Calling exit() is definitely the wrong thing to do in this context. Returning EINVAL when argc > 8 would fix both of these problems. I wonder if you couldn't somehow macro-ize this to fail at build time if argc was greater than 8? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-06-18 14:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-15 14:49 [Bug ports/14250] New: " carlos_odonell at mentor dot com 2012-06-16 3:56 ` [Bug ports/14250] " vapier at gentoo dot org 2012-06-18 14:19 ` carlos_odonell at mentor dot com [this message] 2012-06-18 21:42 ` bugdal at aerifal dot cx 2014-02-17 18:17 ` [Bug libc/14250] [ia64] " jsm28 at gcc dot gnu.org 2014-06-25 10:54 ` fweimer at redhat dot com 2024-01-08 20:09 ` cvs-commit at gcc dot gnu.org 2024-01-09 2:47 ` adhemerval.zanella at linaro dot org 2024-01-09 2:52 ` adhemerval.zanella at linaro dot org
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=bug-14250-131-diThmPSpfb@http.sourceware.org/bugzilla/ \ --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).