Skip to content
  1. Sep 15, 2011
    • Anna Zaks's avatar
      [analyzer] Refactor: make PathDiagnosticLocation responsible for validation of... · 3a769bd9
      Anna Zaks authored
      [analyzer] Refactor: make PathDiagnosticLocation responsible for validation of SourceLocations (commit 2 of ?):
      - Modify all PathDiagnosticLocation constructors that take Stmt to also requre LocationContext.
      - Add a constructor which should be used in case there is no valid statement/location (it will grab the location of the enclosing function).
      
      llvm-svn: 139763
      3a769bd9
  2. Sep 14, 2011
    • Anna Zaks's avatar
      [analyzer] After CFG has been linearized, we can have a situation where an... · 615e3a69
      Anna Zaks authored
      [analyzer] After CFG has been linearized, we can have a situation where an ExpoledNode has an invalid SourceLocation (which has no correspondence in the source code). This commit is the first step to solve this problem.
       - It adds LocationContext to the PathDiagnosticLocation object and uses it to lookup the enclosing statement with a valid location.
       - So far, the LocationContext is only available when the object is constructed from the ExplodedNode.
       - Already found some subtle bugs(in plist-output-alternate.m) where the intermediate diagnostic steps were not previously shown. 
      
      llvm-svn: 139703
      615e3a69
    • Anna Zaks's avatar
      [analyzer] Refactor: Make PathDiagnosticLocation responsible for creating a... · 2c65eea9
      Anna Zaks authored
      [analyzer] Refactor: Make PathDiagnosticLocation responsible for creating a valid object given an ExploadedNode (the same logic can be reused by other checkers).
      
      llvm-svn: 139672
      2c65eea9
  3. Sep 13, 2011
  4. Sep 12, 2011
  5. Sep 10, 2011
  6. Sep 09, 2011
  7. Sep 03, 2011
  8. Sep 02, 2011
  9. Sep 01, 2011
  10. Aug 31, 2011
  11. Aug 29, 2011
  12. Aug 28, 2011
  13. Aug 27, 2011
  14. Aug 26, 2011
  15. Aug 25, 2011
Loading