search for: leaksanitizer

64bit Fedora Failing Tests (8): LeakSanitizer-AddressSanitizer :: TestCases/cleanup_in_tsd_destructor.cc LeakSanitizer-AddressSanitizer :: TestCases/disabler.cc LeakSanitizer-AddressSanitizer :: TestCases/disabler_in_tsd_destructor.cc LeakSanitizer-AddressSanitizer :: TestCases/ignore_object.cc LeakSanitizer-Standalone :: TestC...

On Friday, July 31, 2015 07:50 AM, Hans Wennborg wrote: > Dear testers, > > 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the > sftp, and report results to this thread. LNT is looking good on Ubuntu 14.04 x64, uploaded: clang+llvm-3.7.0-rc2-x86_64-linux-gnu-ubuntu-14.04.tar.xz The errors reported during build are: Failing Tests (17):

On Thu, Dec 26, 2013 at 2:40 AM, Kostya Serebryany <kcc at google.com> wrote: > Like this? > > +extern "C" { > +// Disable LeakSanitizer, see http://llvm.org/bugs/show_bug.cgi?id=18325. > We don't often reference bugs in comments. I would give a brief summary in the text of the comment, and mention the bug in the commit log. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm...

...ebryany <kcc at google.com> wrote: > On Thu, Dec 26, 2013 at 11:49 AM, Chandler Carruth <chandlerc at google.com> wrote: > > On Thu, Dec 26, 2013 at 2:40 AM, Kostya Serebryany <kcc at google.com> wrote: > Like this? > > +extern "C" { > +// Disable LeakSanitizer, see http://llvm.org/bugs/show_bug.cgi?id=18325. > > We don't often reference bugs in comments. I would give a brief summary in the text of the comment, and mention the bug in the commit log. > This? > > +extern "C" { > +// Disable LeakSanitizer for this binary a...

On Mon, Jul 20, 2015 at 2:37 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 20 Jul 2015, at 22:50, Hans Wennborg <hans at chromium.org> wrote: >> >> On Sat, Jul 18, 2015 at 3:17 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote: >>>> >>>> On Thu,

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom

...etpass.cc > SanitizerCommon-msan :: Linux/signal_segv_handler.cc > SanitizerCommon-msan :: Posix/decorate_proc_maps.cc > SanitizerCommon-tsan :: Linux/getpass.cc > SanitizerCommon-tsan :: Posix/decorate_proc_maps.cc > > From Nikola on Fedora 22 x64: > > LeakSanitizer-AddressSanitizer :: TestCases/cleanup_in_tsd_destructor.cc > LeakSanitizer-AddressSanitizer :: TestCases/disabler.cc > LeakSanitizer-AddressSanitizer :: TestCases/disabler_in_tsd_destructor.cc > LeakSanitizer-AddressSanitizer :: TestCases/ignore_object.cc > LeakSanitizer...

Dear testers, 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the sftp, and report results to this thread. A lot of fixes have been applied since rc1, both to the build script and the code in general, so hopefully it will be less bumpy this time. >From this point, I will no longer accept merge requests to finish existing features; it's now bug-fixes only. Thanks again

....cc AddressSanitizer-mips64-linux :: TestCases/Posix/coverage-direct.cc AddressSanitizer-mips64-linux :: TestCases/Posix/coverage-fork-direct.cc AddressSanitizer-mips64-linux :: TestCases/Posix/coverage.cc DataFlowSanitizer :: custom.cc DataFlowSanitizer :: propagate.c LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc LeakSanitizer-Standalone :: TestCases/swapcontext.cc LeakSanitizer-Standalone :: TestCases/use_registers.cc MemorySanitizer :: Linux/process_vm_readv.cc MemorySanitizer...

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release

I get leaks from a system library: ==16272==ERROR: LeakSanitizer: detected memory leaks Direct leak of 148 byte(s) in 2 object(s) allocated from: #0 0x4a3172 in __interceptor_malloc .../build/../projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3 #1 0x7f575d8df1fe in wcsdup (/lib64/libedit.so.0+0x1c1fe) I don't think I can fix this... ;] -Chan...

In the file \lib\Support\Process.cpp on line 60, it seems as though an unnecessary heap allocation and memory leak occurs. This is the offending code: static TimeValue getElapsedWallTime() { static TimeValue &StartTime = *new TimeValue(TimeValue::now()); return TimeValue::now() - StartTime; } The issue is that the StartTime variable's value is allocated on the heap, after which a

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

...> > leak check tblgen, but that would be a runtime flag, not build time) >> > >> > On Wednesday, December 25, 2013 7:08:27 AM, Kostya Serebryany >> > <kcc at google.com> wrote: >> > >> > Hi, >> > >> > We are trying to enable LeakSanitizer on our asan/msan llvm bootstrap >> bot >> > >> > (http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/). >> > >> > In clang itself there are two leaks >> > >> > (http://llvm.org/bugs/show_bug.cgi?id=18318, >> > http...

Hi, We are trying to enable LeakSanitizer on our asan/msan llvm bootstrap bot (http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/). In clang itself there are two leaks (http://llvm.org/bugs/show_bug.cgi?id=18318, http://llvm-reviews.chandlerc.com/D2472) and one lsan-hostile feature (http://llvm.org/bugs/show_bug.cgi?id=183...

...verage-direct.cc > AddressSanitizer-mips64-linux :: TestCases/Posix/coverage-fork-direct.cc > AddressSanitizer-mips64-linux :: TestCases/Posix/coverage.cc > DataFlowSanitizer :: custom.cc > DataFlowSanitizer :: propagate.c > LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc > LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc > LeakSanitizer-Standalone :: TestCases/swapcontext.cc > LeakSanitizer-Standalone :: TestCases/use_registers.cc > MemorySanitizer :...

...tr" ## I get in the interactive mode of R for n <- 4 ## the number is unimportant split.screen(c(n, n)) ## close.screen(all=TRUE) ## this command does not rectify the problem q() ## the following result: ================================================================= ==14567==ERROR: LeakSanitizer: detected memory leaks Direct leak of 32 byte(s) in 1 object(s) allocated from: #0 0x4d5018 (/usr/local/lib64/R/bin/exec/R+0x4d5018) #1 0x7f61cec8b56a (/usr/lib/x86_64-linux-gnu/libcairo.so.2+0x9b56a) SUMMARY: AddressSanitizer: 32 byte(s) leaked in 1 allocation(s). ## I use Ubuntu 14....

The asan bootstrap bot is unhappy with lld. Rui, os someone, please take a look. http://lab.llvm.org:8011/builders/sanitizer-x86_64- linux-bootstrap/builds/138/steps/check-lld%20asan/logs/stdio ==26011==ERROR: LeakSanitizer: detected memory leaks Direct leak of 184 byte(s) in 1 object(s) allocated from: #0 0x72fab0 in operator new(unsigned long) /mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:82 #1 0x8c8610 in void lld::elf::BinaryFile::p...

...lvm-dev at lists.llvm.org> wrote: >> The asan bootstrap bot is unhappy with lld. >> Rui, os someone, please take a look. >> >> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/138/steps/check-lld%20asan/logs/stdio >> >> ==26011==ERROR: LeakSanitizer: detected memory leaks >> >> Direct leak of 184 byte(s) in 1 object(s) allocated from: >> #0 0x72fab0 in operator new(unsigned long) >> /mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:82 >>...

I updated a powerpc64 be system from fedora 25 (glibc 2.24) to fedora 26 (glibc 2.25) and several test cases started failing that deal with dynamic thread local storage. Failing Tests (3): LeakSanitizer-AddressSanitizer-powerpc64 :: TestCases/Linux/use_tls_dynamic.cc LeakSanitizer-Standalone-powerpc64 :: TestCases/Linux/use_tls_dynamic.cc MemorySanitizer-POWERPC64 :: dtls_test.c I looked at dtls_test.c in detail ******************** TEST 'MemorySanitizer-POWERPC64 :: dtls_test.c...