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] New: ia64 makecontext.c writes to stderr and it should not. Date: Fri, 15 Jun 2012 14:49:00 -0000 [thread overview] Message-ID: <bug-14250-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14250 Bug #: 14250 Summary: ia64 makecontext.c writes to stderr and it should not. Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: ports AssignedTo: unassigned@sourceware.org ReportedBy: carlos_odonell@mentor.com CC: carlos@systemhalted.org, roland@gnu.org, vapier@gentoo.org Classification: Unclassified Host: ia64-linux-gnu Target: ia64-linux-gnu Build: ia64-linux-gnu The implementation of makecontext() for ia64 (ports/sysdeps/unix/sysv/linux/ia64/makecontext.c) writes to stderr if there are more than 8 arguments. The function should not write to stderr, see bug #13983 for some background. Instead the function should set errno and return. Unfortunately POSIX doesn't seem to dictate any errno for makecontext(), almost as if it should never fail. This is IMO an oversight, we should return EINVAL when > 8 arguments. At least IBM's XL C runtime returns EINVAL with invalid argc. We must strive for a high QoI and avoid arbitrarily writing to stderr. -- 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 reply other threads:[~2012-06-15 14:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-15 14:49 carlos_odonell at mentor dot com [this message] 2012-06-16 3:56 ` [Bug ports/14250] " vapier at gentoo dot org 2012-06-18 14:19 ` carlos_odonell at mentor dot com 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@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).