search for: wrongfreetest

Displaying 7 results from an estimated 7 matches for "wrongfreetest".

2017 Jul 31
3
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
...AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.UseThenFreeThenUseTest (2542 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.WrongFreeTest (2546 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-with-calls-Test/AddressSanitizer.DoubleFreeTest (2589 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-with-calls-Test/AddressSanitizer.ReallocFreedPointerTest (2615 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-wi...
2017 Jul 26
15
[5.0.0 Release] Release Candidate 1 tagged
Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans
2017 Jul 31
0
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
...Sanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616) >> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.UseThenFreeThenUseTest (2542 of 38616) >> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.WrongFreeTest (2546 of 38616) ... > Do we know what's up with all of these ASan failures? Is there a bug for it? I spent a limited amount of debugging on it, but the common problem is that on i386 (aka 32-bit x86) all programs compiled with -fsanitize=address now die with: ==11122==AddressSanitizer CHEC...
2018 Jun 04
5
6.0.1-rc2 has been tagged
Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom
2018 Apr 26
7
6.0.1-rc1 has been tagged
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
2018 Feb 09
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
...86-calls-Test/AddressSanitizer.DoubleFreeTest AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.ReallocFreedPointerTest AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.UseThenFreeThenUseTest AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.WrongFreeTest AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.DoubleFreeTest AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.UseThenFreeThenUseTest AddressSanitizer-Unit :...
2018 Feb 09
2
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
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. >> >>