[compiler-rt] r271786 - Ok, now I know why I kept getting confused and not making progress

[Chandler Carruth via llvm-commits]

Author: chandlerc
Date: Sat Jun  4 03:54:57 2016
New Revision: 271786

URL: http://llvm.org/viewvc/llvm-project?rev=271786&view=rev
Log:
Ok, now I know why I kept getting confused and not making progress
fixing tis test. There are different configurations running, and they
have subtly different backtraces. I didn't notice that the configs
changed and so I kept occilating between the two.

Now I've looked at two different configs at the same time, and so this
should be much more likely to work.

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=271786&r1=271785&r2=271786&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:54:57 2016
@@ -20,7 +20,13 @@ 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 {{.*}} in __asan_wrap_strdup
-// CHECK:   #1 {{.*}} in main {{.*}}intercept_strdup.cc:[[@LINE-15]]
+//
+// The first frame is our wrapper normally but will be malloc in the dynamic
+// config.
+// CHECK:   #0 {{.*}} in {{malloc|__asan_wrap_strdup}}
+//
+// The local call to _strdup above may be the second or third frame depending
+// on whether we're using the dynamic config.
+// CHECK:   #{{[12]}} {{.*}} in main {{.*}}intercept_strdup.cc:[[@LINE-21]
   free(ptr);
 }