Comment #2 on issue 253 by [email protected]: Correctly handle the
symbolizer pipe on fork()
http://code.google.com/p/address-sanitizer/issues/detail?id=253
Currently symbolizer set up pipes and spawns new subprocess "on demand". We
can indeed implement an "easy fix" and add a method that would close the
pipes, and then call it in the child subprocess immediately after fork
(though, looks like this machinery is available only in TSan). I don't
fully understand the second suggested approach - it's kind of dangerous to
spawn new threads in programs that could potentially be forked, isn't it?
The symbolizer *does* grab a lock.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
