On 03/02/2015 12:44 PM, Martin Ri wrote:
Hi,
has anyone seen reports like the one below? A stack-buffer-overflow is
reported, but the memory is addressable.
Notes: I have seen similar instances reported as "unknown-crash". Looking
at the code in asan-report.cc, this is the initial error code, and the real
error is determined by looking at the shadow. So it seems this could be
some data race: When the shadow is initially checked as part of the
instrumented code, the memory is marked as invalid and error reporting is
triggered. But shortly afterwards it gets marked as valid.
Hi Martin,
We have seen something like this in KASan. But there it was clearly
caused by use-after-return which is not obvious in your case.
-Y
--
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.
