On 12/18/2014 08:29 PM, Robert Henry wrote:
I've compiled and run a large program under the address sanitizer. I have
two code paths involving asprintf or vasprintf wherein asan detects a fault
when the value returned from asprintf/vasprintf is freed. In one case,
asan complains about a double-free; in another case asan complains about an
illegal free.
My attempts to reproduce this with a small test case have failed.
Before I spend more time on reproducing this, I was wondering if
asprintf/vasprintf were known to be problematic?
I don't think so. AFAIK these interceptors simply forward you result of
malloc call without any modifications (besides checking the format string).
-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.
