en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c#5e04b539 [compiler-rt] Try again to correct test after 3f1a9b7eca0 added segment names to objdump outputOne check was missed on the previous attempt List of files: /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c Fri, 04 Sep 2020 22:48:27 +0000 Daniel Sanders <daniel_l_sanders@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c#1eae19a8 [compiler-rt] Try to correct test after 3f1a9b7eca0 added segment names to objdump output List of files: /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c Fri, 04 Sep 2020 19:23:49 +0000 Daniel Sanders <daniel_l_sanders@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c#bf6e7848 [asan] Move instrumented null-terminated strings to a special section, compiler-rt partOn Darwin, simple C null-terminated constant strings normally end up in the __TEXT,__cstring section of the resulting Mach-O binary. When instrumented with ASan, these strings are transformed in a way that they cannot be in __cstring (the linker unifies the content of this section and strips extra NUL bytes, which would break instrumentation), and are put into a generic __const section. This breaks some of the tools that we have: Some tools need to scan all C null-terminated strings in Mach-O binaries, and scanning all the contents of __const has a large performance penalty. This patch instead introduces a special section, __asan_cstring which will now hold the instrumented null-terminated strings.Differential Revision: https://reviews.llvm.org/D25026llvm-svn: 285620 List of files: /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/cstring_section.c Mon, 31 Oct 2016 18:52:32 +0000 Kuba Brecka <kuba.brecka@gmail.com>