Comment #4 on issue 331 by [email protected]: Problem with opendir
/ fstatfs in Firefox on Mac OSX
http://code.google.com/p/address-sanitizer/issues/detail?id=331
If you're ok with building a custom Clang, I'd try to insert a Print() or
Report() call into the fstatfs interceptor to dump the contents of the
memory before the call to REAL(fstatfs)() (see
projects/compiler-rt/lib/sanitizer_common/sanitizer_common_interceptors.inc)
BTW there's the following warning in the interceptor:
3068 // FIXME: under ASan the call below may write to freed memory and
corrupt
3069 // its metadata. See
3070 // https://code.google.com/p/address-sanitizer/issues/detail?id=321.
It shouldn't bother you as your report happens on a stack-allocated memory
(never saw a stack address like 0x000119101c00 before, but vmmap says it's
possible)
--
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.
