public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kees at outflux dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/9854] glibc opens up new tty to print *** %n in writable segment detected *** Date: Fri, 11 Sep 2009 20:03:00 -0000 [thread overview] Message-ID: <20090911200259.27608.qmail@sourceware.org> (raw) In-Reply-To: <20090217003308.9854.walch.martin@web.de> ------- Additional Comments From kees at outflux dot net 2009-09-11 20:02 ------- glibc attempts to write to the controlling terminal, in the hopes that it will be noticed at the highest possible level. Especially since a process may have closed its stderr already. To explicitly disable this and try to write to fd 2, you can set the environment variable LIBC_FATAL_STDERR_=1 (yes, there is a trailing underscore in the variable name). -- http://sourceware.org/bugzilla/show_bug.cgi?id=9854 ------- 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:[~2009-09-11 20:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-17 0:33 [Bug libc/9854] New: " walch dot martin at web dot de 2009-02-17 1:42 ` [Bug libc/9854] " drepper at redhat dot com 2009-02-17 8:38 ` walch dot martin at web dot de 2009-09-11 20:03 ` kees at outflux dot net [this message] [not found] <bug-9854-131@http.sourceware.org/bugzilla/> 2014-07-01 20:53 ` fweimer 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=20090911200259.27608.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).