Comment #6 on issue 253 by [email protected]: Correctly handle the
symbolizer pipe on fork()
http://code.google.com/p/address-sanitizer/issues/detail?id=253
For Chromium we need to prefork a single symbolizer before the sandbox is
turned on (new processes may appear after that, but newly forked
symbolizers won't be able to open files).
The idea is to keep an open socket to the symbolizer that a new Chrome
process will use to request an exclusive pipe/socketpair to interact with
the symbolizer process.
It actually doesn't matter how many threads we're going to have in the
symbolizer.
--
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.
