This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13983] __libc_message() shouldn't blindly write to STDERR_FILENO
- From: "ppluzhnikov at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 16 Apr 2012 05:59:03 +0000
- Subject: [Bug libc/13983] __libc_message() shouldn't blindly write to STDERR_FILENO
- Auto-submitted: auto-generated
- References: <bug-13983-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13983
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppluzhnikov at google dot
| |com
--- Comment #5 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2012-04-16 05:59:03 UTC ---
(In reply to comment #4)
> Personally, I would flag this INVALID.
In addition, dumping messages to /dev/tty is just plain wrong.
I run some nightly builds from cron, and redirect their stdout/stderr.
Recently I discovered that if I run the same build by hand, I get several error
messages in my terminal. I have *no clue* which commands they are coming from.
They are *not* useful.
(Now that I looked at __libc_message, I am going to set LIBC_FATAL_STDERR_ in
the environment to direct them back 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.