http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59136
--- Comment #4 from Alexey Samsonov ---
(In reply to Jakub Jelinek from comment #3)
> (In reply to Alexey Samsonov from comment #2)
> > We found it convenient to run fork+exec early at program startup. It can
> > also be slightly dangerous to call
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59136
--- Comment #3 from Jakub Jelinek ---
(In reply to Alexey Samsonov from comment #2)
> We found it convenient to run fork+exec early at program startup. It can
> also be slightly dangerous to call fork() in multi-threaded program (even
> though we
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59136
--- Comment #2 from Alexey Samsonov ---
(In reply to Jakub Jelinek from comment #0)
> I've noticed that libasan/liblsan now start external llvm-symbolizer for all
> programs just in case they would be buggy, that looks like a very bad idea
> to me
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59136
Kostya Serebryany changed:
What|Removed |Added
CC||glider at google dot com,
