Comment #7 on issue 255 by [email protected]: Forking threads fails
with clang 3.4
http://code.google.com/p/address-sanitizer/issues/detail?id=255
I still perfectly agree that mixing fork and threads in the general case
is
dangerous. However, I also still believe that my use case is perfectly
valid: I use
fork() as a way to take a snapshot of the memory of my database in order
to be able
to make a snapshot while still accepting updates in the parent process (I
don't
think there is a better solution for this).
Side note: this is how process snapshotting works in Breakpad (an error
reporting system used by Chromium). I don't think we want to prohibit this
pattern.
--
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/groups/opt_out.
