to various unix/posix functions, e.g. 'open()'.

As a first check, check that when 'open()' is passed 'O_CREAT' that it has
a third argument.

llvm-svn: 97086

llvm-svn: 97085

llvm-svn: 97084

llvm-svn: 97083

llvm-svn: 97082

pointer (for defensive programming).  This matches the behavior with
assigning NULL to a regular pointer.  Fixes <rdar://problem/7631278>.

llvm-svn: 96985

in the static analyzer.

llvm-svn: 96539

llvm-svn: 96537

current stack frame.

When leaving a callee, remove all bindings belonging to that callee.

llvm-svn: 96473

For inline-based inter-procedural analysis, we will have multiple stack space regions. Use a dense map to store them.

llvm-svn: 96472

llvm-svn: 96341

to evaluate arguments.

llvm-svn: 96293

the LLVMConventionsChecker.

llvm-svn: 96202

that allocate heap memory.

llvm-svn: 96184

of operating on each code decl.  This exposes two flaws in AnalysisConsumer
that should eventually be fixed:

(1) It is not possible to associate multiple "actions" with a single
    command line argument.  This will require the notion of an
	"analysis" group, and possibly tablegen support.  (although eventually
    we want to support dynamically loading analyses as well)

(2) AnalysisConsumer may not actually be scanning the declarations in namespaces.
    We'll experiment first in LLVMConventionsChecker before changing the
    behavior in AnalysisConsumer.

llvm-svn: 96183

llvm-svn: 96181

No functionality change.

llvm-svn: 96180

llvm-svn: 96154

Currently these checks are intended to be largely syntactical, but may get more
sophisticated over time.

As an initial foray into this brave new world, emit a static analyzer warning
when binding a temporary 'std::string' to an 'llvm::StringRef' where the
lifetime of the 'std::string' does not outlive the 'llvm::StringRef'.

llvm-svn: 96147

by scanning through the values of LazyCompoundVals.

llvm-svn: 96067

No functionality change.

llvm-svn: 96060

and CXXRecordDecl::getDefinition(); it's totally unnecessary. No
functionality change.

llvm-svn: 95836

llvm-svn: 95755

NULL, not the store, to determine if a lookup succeeded.  The store
can be null if it contained no bindings.  This fixes a false positive
reported to me by a user of the analyzer.

llvm-svn: 95679

llvm-svn: 95563

llvm-svn: 95561

llvm-svn: 95552

llvm-svn: 95547

3 files changed, 76 insertions(+), 153 deletions(-)

llvm-svn: 95546

llvm-svn: 95545

        GRState::getSVal(MemRegion*) => Load().

llvm-svn: 95541

llvm-svn: 95540

alloca region.

llvm-svn: 95539

It's more sophisticated than the original one of BasicStore. But it does
matter. 

llvm-svn: 95536

llvm-svn: 95535

llvm-svn: 95534

llvm-svn: 95531

llvm-svn: 95529

Also teach RegionStore::RetrieveVar() to handle 'static' pointers that are implicitly initialized to NULL.

llvm-svn: 95479

Fix regression in RegionStore (from BasicStore) where static variables were not treated as being implicitly initialized to 0 (and instead were getting symbolicated).

llvm-svn: 95478