hello
1. can you tell me where is the memory scan in source code?(which file?
which class? which function?)
i read the most lsan source code, but i don't find that scan code : (
2. why 64bit platform is ok? a random 8 byte sequences don't like a pointer?
thanks a lot
在
hello
1. can you tell me where is the memory scan in source code?(which file?
which class? which function?)
i read the most lsan source code, but i don't find that scan code : (
2. why 64bit platform is ok? a random 8 byte sequences don't like a pointer?
3. is it possible that we ignore some
On Fri, Nov 28, 2014 at 12:26 PM, wuning shi wuning@gmail.com wrote:
hello
1. can you tell me where is the memory scan in source code?(which file?
which class? which function?)
i read the most lsan source code, but i don't find that scan code : (
ScanRangeForPointers() in
Hello.
The main problem with 32-bit leak checking is that too many random 4-byte
sequences look like pointers.
In order to find live objects in the heap LSan scans the memory that's
already known to be live and looks for pointers in it. Because LSan doesn't
know anything about data types, it has
