Cross Reference: /external/clang/test/Analysis/retain-release-path-notes.m

Lines Matching full:leak
48   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
53   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
61   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
67   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
73   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
105   return; // expected-warning{{leak}} expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
115   return object; // expected-warning{{leak}} expected-note{{Object returned to caller as an owning reference (single retain count transferred to caller)}} expected-note{{Object leaked: object allocated and stored into 'object' is returned from a function whose name ('CFGetRuleViolation') does not contain 'Copy' or 'Create'.  This violates the naming convention rules given in the Memory Management Guide for Core Foundation}}
136   return result; // expected-warning{{leak}} expected-note{{Object returned to caller as an owning reference (single retain count transferred to caller)}} expected-note{{Object leaked: object allocated and stored into 'result' is returned from a method whose name ('getViolation') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'.  This violates the naming convention rules given in the Memory Management Guide for Cocoa}}
226   id x = [[MyObj alloc] initX]; // expected-warning {{Potential leak of an object}}
237   id z = [[MyObj alloc] initZ]; // expected-warning {{Potential leak of an object}}
464 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
466 // CHECK-NEXT:    <key>type</key><string>Leak</string>
610 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
612 // CHECK-NEXT:    <key>type</key><string>Leak</string>
981 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
983 // CHECK-NEXT:    <key>type</key><string>Leak</string>
1202 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
1204 // CHECK-NEXT:    <key>type</key><string>Leak</string>
1423 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
1425 // CHECK-NEXT:    <key>type</key><string>Leak</string>
2678 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;leaked&apos;</string>
2680 // CHECK-NEXT:    <key>type</key><string>Leak</string>
3052 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;object&apos;</string>
3054 // CHECK-NEXT:    <key>type</key><string>Leak of returned object</string>
3800 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object stored into &apos;result&apos;</string>
3802 // CHECK-NEXT:    <key>type</key><string>Leak of returned object</string>
5134 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object</string>
5136 // CHECK-NEXT:    <key>type</key><string>Leak</string>
5488 // CHECK-NEXT:    <key>description</key><string>Potential leak of an object</string>
5490 // CHECK-NEXT:    <key>type</key><string>Leak</string>
OpenGrok
