[cfe-dev] Why clang needs to fork into itself?
Richard
legalize at xmission.com
Mon Jan 27 13:56:13 PST 2014
In article <CAAnoKN971ZHsDU-01s5pqbUK2qKNW=_rJy-t=u7ovDd7kOWFyg at mail.gmail.com>,
Tomasz Mikolajczyk <tmmikolajczyk at gmail.com> writes:
> I haven't see the code but potentially the purpose of forking is to
> handle internal compiler errors, especially the case when the child
> process crashes when processing an input code. That may be easily
> detected and handled properly by the parent process, by collecting the
> trace, logs and by encouraging user to fill an issue in the bug DB,
> etc.
How is this going to work on Windows where fork semantics really aren't
supported?
I've used crash report generator mechanisms on both linux and Windows
that didn't require forking oneself.
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>
More information about the cfe-dev
mailing list