From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: possible getopt stderr output changes
Date: Fri, 12 Dec 2014 22:11:52 -0500 [thread overview]
Message-ID: <20141213031152.GD4574@brightrain.aerifal.cx> (raw)
In-Reply-To: <20141213000223.GA530@muslin>
On Fri, Dec 12, 2014 at 04:02:24PM -0800, Isaac Dunham wrote:
> I realize there's quality of implementation to be concerned about and
> similar issues, but I'm really wondering:
>
> How brain-damaged does code have to be to call getopt() from a thread,
> *after* starting a second thread and beginning writes to stderr?
> Is there any real-world use of this?
The way it's most likely to happen is when something that runs early
in main, or from a global ctor, starts threads, and they encounter
errors to print to stderr. Generally I think any 'library level' use
of stderr (or other standard streams) is bad design and so in my
opinion, this shouldn't happen, but plenty of people disagree.
Rich
next prev parent reply other threads:[~2014-12-13 3:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 0:10 Rich Felker
2014-12-11 3:53 ` Laurent Bercot
2014-12-11 6:44 ` Rich Felker
2014-12-11 15:40 ` Laurent Bercot
2014-12-11 17:51 ` stdio [de]merits discussion [Re: [musl] possible getopt stderr output changes] Rich Felker
2014-12-11 23:05 ` Laurent Bercot
2014-12-11 23:35 ` Rich Felker
2014-12-12 2:33 ` Morten Welinder
2014-12-11 22:07 ` possible getopt stderr output changes Rich Felker
2014-12-13 0:02 ` Isaac Dunham
2014-12-13 3:11 ` Rich Felker [this message]
2014-12-19 21:49 ` Rich Felker
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=20141213031152.GD4574@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).