From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: LLVM testsuite, close-stderr.ll hangs
Date: Tue, 18 Dec 2012 01:14:01 -0500 [thread overview]
Message-ID: <20121218061401.GV20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <50D0056A.4090303@ojab.ru>
On Tue, Dec 18, 2012 at 09:55:54AM +0400, ojab wrote:
> On 17.12.2012 21:22, Rich Felker wrote:
> >On Mon, Dec 17, 2012 at 11:58:29AM -0500, Rich Felker wrote:
> >To track this down, you could run under gdb and just interrupt the
> >program and look at a backtrace once it hangs. This should make it
> >clear whether exit was called recursively.
>
> Looks something like that (gdb output in the attached file, `bt`
> while `opt` hangs in the bottom): I've set `break exit` and stepped
> till it hangs, first exit() happens in command line parsing (https://github.com/llvm-mirror/llvm/blob/master/lib/Support/CommandLine.cpp#L846),
> which calls report_fatal_error("IO failure on output stream.");,
> which calls exit itself.
>
> Looks like (note that I'm barely know C/C++) something wrong in
> ostream destruction: after changing ifdef to ifndef @
> https://github.com/llvm-mirror/llvm/blob/master/lib/Support/raw_ostream.cpp#L501
> all works as it should:
I suspect there may be similar problems in more places than just this.
It definitely calls for a bug report. Calling exit from global dtors
is invalid (invokes undefined behavior).
Rich
next prev parent reply other threads:[~2012-12-18 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:03 ojab
2012-12-17 16:58 ` Rich Felker
2012-12-17 17:22 ` Rich Felker
2012-12-18 5:55 ` ojab
2012-12-18 6:14 ` Rich Felker [this message]
2012-12-18 6:37 ` ojab
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=20121218061401.GV20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).