Re: Issue 62 in memory-sanitizer: Origin tracking is not async signal safe

[memory-s...@googlecode.com]

Updates:
Summary: Origin tracking is not async signal safe

Comment #3 on issue 62 by euge...@google.com: Origin tracking is not async
signal safe
https://code.google.com/p/memory-sanitizer/issues/detail?id=62

What's left to fix here is __msan_set_alloca_origin4 going into chained
origin depot. This is (a) inefficient and (b) async signal unsafe.

--
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

[memory-s...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 62 by euge...@google.com: Origin tracking is not async
signal safe
https://code.google.com/p/memory-sanitizer/issues/detail?id=62

This has been fixed a while back in r223233.