search for: deep_call_stack

Rafael, Filipe, I am looking at the fixes you apply to sanitizer tests and they worry me. (e.g. https://reviews.llvm.org/D31498) The fixes are mostly mechanical and thus every single change looks safe, but given the amount of changes there is large risk to cripple some of the tests in a way that they will stop detecting failures. When I write a test for new functionality, I always verify that

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/coverage-reset.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/coverage.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/current_allocated_bytes.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/deep_call_stack.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/deep_thread_stack.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/dlclose-test.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/fread_fwrite.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>