File: max-nodes-suppress-on-sink.cpp

package info (click to toggle)
llvm-toolchain-7 1%3A7.0.1-8
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 733,456 kB
  • sloc: cpp: 3,776,651; ansic: 633,271; asm: 350,301; python: 142,716; objc: 107,612; sh: 22,626; lisp: 11,056; perl: 7,999; pascal: 6,742; ml: 5,537; awk: 3,536; makefile: 2,557; cs: 2,027; xml: 841; ruby: 156
file content (34 lines) | stat: -rw-r--r-- 1,029 bytes parent folder | download | duplicates (28)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
// RUN: %clang_analyze_cc1 -x c++ -fcxx-exceptions -analyzer-checker=core,unix.Malloc,debug.ExprInspection -analyzer-config max-nodes=12 -verify %s

// Here we test how "suppress on sink" feature of certain bugtypes interacts
// with reaching analysis limits. See comments in max-nodes-suppress-on-sink.c
// for more discussion.

typedef __typeof(sizeof(int)) size_t;
void *malloc(size_t);

void clang_analyzer_warnIfReached(void);

// Because we don't have a better approach, we currently treat throw as
// noreturn.
void test_throw_treated_as_noreturn() {
  void *p = malloc(1); // no-warning

  clang_analyzer_warnIfReached(); // expected-warning{{REACHABLE}}
  clang_analyzer_warnIfReached(); // no-warning

  throw 0;
}

// FIXME: Handled throws shouldn't be suppressing us!
void test_handled_throw_treated_as_noreturn() {
  void *p = malloc(1); // no-warning

  clang_analyzer_warnIfReached(); // expected-warning{{REACHABLE}}
  clang_analyzer_warnIfReached(); // no-warning

  try {
    throw 0;
  } catch (int i) {
  }
}