Comment #19 on issue 148 by [email protected]: failing to intercept
strdup
https://code.google.com/p/address-sanitizer/issues/detail?id=148
I don't think people are hijacking the bug - I think attributing this issue
version scripts was inaccurate to begin with. The root cause seems to be
ASAN simply not properly intercepting strdup under any conditions. I'm
noticing the same symptoms on my system and we're not using version
scripts. Additionally, the call stack for strdup looks identical to the
examples presented so far - __GI___strdup is called - even without the use
of version scripts.
IMHO, this is a true ASAN bug and it's affecting a lot of code using gcc
4.8.0+ now because the GCC team has made it available through the
-fsanitize=address flag. Of course, we can always not use that flag, but is
that what you guys really want?
--
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.
