| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
TODO: support realloc(). Currently it is not possible due to the present realloc() handling. Currently RegionState is not being attached to realloc() in case of a zero Size argument.
llvm-svn: 234889
|
| |
|
|
|
|
|
|
|
|
| |
+ separate bug report for "Free alloca()" error to be able to customize checkers responsible for this error.
+ Muted "Free alloca()" error for NewDelete checker that is not responsible for c-allocated memory, turned on for unix.MismatchedDeallocator checker.
+ RefState for alloca() - to be able to detect usage of zero-allocated memory by upcoming ZeroAllocDereference checker.
+ AF_Alloca family to handle alloca() consistently - keep proper family in RefState, handle 'alloca' by getCheckIfTracked() facility, etc.
+ extra tests.
llvm-svn: 229850
|
| |
|
|
|
|
| |
package.
llvm-svn: 220289
|
| |
|
|
|
|
| |
As per Ted’s suggestion!
llvm-svn: 178938
|
| |
|
|
|
|
|
|
| |
As mentioned in the previous commit message, the use-after-free and
double-free warnings for 'delete' are worth enabling even while the
leak warnings still have false positives.
llvm-svn: 178891
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This splits the leak-checking part of alpha.cplusplus.NewDelete into a
separate user-level checker, alpha.cplusplus.NewDeleteLeaks. All the
difficult false positives we've seen with the new/delete checker have been
spurious leak warnings; the use-after-free warnings and mismatched
deallocator warnings, while rare, have always been valid.
<rdar://problem/6194569>
llvm-svn: 178890
|
| |
|
|
|
|
|
| |
Missed check added to testMallocFreeNoWarn().
Removed FIXMEs as the current behaviour is considered acceptable now.
llvm-svn: 178824
|
| |
|
|
| |
llvm-svn: 178529
|
| |
|
|
| |
llvm-svn: 178398
|
| |
|
|
| |
llvm-svn: 178397
|
|
|
+ Refactoring.
llvm-svn: 178388
|
