[compiler-rt] r271783 - I didn't actually get this right, but now I have frame #0 and frame #2.

[Chandler Carruth via llvm-commits]

Author: chandlerc
Date: Sat Jun  4 03:09:24 2016
New Revision: 271783

URL: http://llvm.org/viewvc/llvm-project?rev=271783&view=rev
Log:
I didn't actually get this right, but now I have frame #0 and frame #2.
This should fail on frame #1 and show what that should actually be.

Modified:
    compiler-rt/trunk/test/asan/TestCases/Windows/intercept_strdup.cc

Modified: compiler-rt/trunk/test/asan/TestCases/Windows/intercept_strdup.cc
URL: http://llvm.org/viewvc/llvm-project/compiler-rt/trunk/test/asan/TestCases/Windows/intercept_strdup.cc?rev=271783&r1=271782&r2=271783&view=diff
==============================================================================
--- compiler-rt/trunk/test/asan/TestCases/Windows/intercept_strdup.cc (original)
+++ compiler-rt/trunk/test/asan/TestCases/Windows/intercept_strdup.cc Sat Jun  4 03:09:24 2016
@@ -20,7 +20,8 @@ int main() {
 // CHECK:   {{#0 .* main .*}}intercept_strdup.cc:[[@LINE-3]]
 // CHECK: [[ADDR]] is located 1 bytes to the left of 6-byte region
 // CHECK: allocated by thread T0 here:
-// CHECK:   #0 {{.*strdup}}
-// CHECK:   #1 {{.* main .*}}intercept_strdup.cc:[[@LINE-15]]
+// CHECK:   #0 {{.*}} in malloc
+// CHECK:   #1 {{.*FIXME}}
+// CHECK:   #2 {{.* main .*}}intercept_strdup.cc:[[@LINE-15]]
   free(ptr);
 }