6 Commits

Author	SHA1	Message	Date
Ted Kremenek	5df037e808	Tweak stack address checker to report multiple cases where globals may reference stack memory. ... Also refactor the diagnostics so that we print out the kind of stack memory returned. llvm-svn: 106210	2010-06-17 04:21:37 +00:00
Ted Kremenek	17504bea33	Rework StackAddrLeakChecker to find stores of stack memory addresses to global variables ... by inspecting the Store bindings instead of iterating over all the global variables in a translation unit. By looking at the store directly, we avoid cases where we cannot directly load from the global variable, such as an array (which can result in an assertion failure) and it also catches cases where we store stack addresses to non-scalar globals. Also, but not iterating over all the globals in the translation unit, we maintain cache locality, and the complexity of the checker becomes restricted to the complexity of the analyzed function, and doesn't scale with the size of the translation unit. This fixes PR 7383. llvm-svn: 106184	2010-06-17 00:24:44 +00:00
Zhongxing Xu	abd60dd1fc	We return Loc where we know. ... llvm-svn: 106087	2010-06-16 06:16:46 +00:00
Zhongxing Xu	1225aacacf	Merge StackAddrLeakChecker and ReturnStackAddressChecker. ... llvm-svn: 105687	2010-06-09 06:08:24 +00:00
Zhongxing Xu	4200be5e76	Directly compare the StackFrameContext. This greatly simplifies logic and ... improves generality. Thanks Ted. llvm-svn: 105686	2010-06-09 05:50:38 +00:00
Zhongxing Xu	87e7fc5dc2	Add a checker check if a global variable holds a local variable's address after ... the function call is left where the local variable is declared. llvm-svn: 105602	2010-06-08 10:00:00 +00:00