Displaying 6 results from an estimated 6 matches for "20asan".
2014 Sep 10
4
[LLVMdev] Leaks in PBQPBuilderWithCoalescing::build ?
...e:
>>
>> Hi Lang,
>>
>>
>>
>> For your information, the leak sanitizer found something when I committed
>> my patch:
>>
>>
>>
>>
>> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/4506/steps/check-llvm%20asan/logs/stdio
>>
>>
>>
>> I will try to have a look at it.
>>
>>
>>
>> Cheers,
>>
>> --
>>
>> Arnaud A. de Grandmaison
>>
>>
>>
>>
>>
>> _______________________________________________
>>...
2014 Sep 10
4
[LLVMdev] Leaks in PBQPBuilderWithCoalescing::build ?
...ed, Sep 10, 2014 at 11:23 AM, Arnaud A. de Grandmaison <arnaud.degrandmaison at arm.com> wrote:
Hi Lang,
For your information, the leak sanitizer found something when I committed my patch:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/4506/steps/check-llvm%20asan/logs/stdio
I will try to have a look at it.
Cheers,
--
Arnaud A. de Grandmaison
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140910/239f0d00/attachment.html>
2016 Nov 11
2
initialization-order-fiasco in MCTargetDesc/X86MCAsmInfo.cpp
Mehdi, Teresa,
Not sure if this is caused by one of your recent commits, or by someone
else's,
please excuse me if that's unrelated to your work...
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/542/steps/check-llvm%20asan/logs/stdio
==26383==ERROR: AddressSanitizer: initialization-order-fiasco on
address 0x000002ef41d8 at pc 0x0000009d1aa5 bp 0x7ffd0cd72b50 sp
0x7ffd0cd72b48
READ of size 4 at 0x000002ef41d8 thread T0
#0 0x9d1aa4 in getValue
/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/inclu...
2016 Nov 08
2
leaks in lld on the bot
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
#...
2016 Nov 08
3
leaks in lld on the bot
...t 4:43 PM, Kostya Serebryany via llvm-dev
> <llvm-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/proje...
2014 Feb 21
12
[LLVMdev] asan coverage
>
>
>
> We may need some additional info.
What kind of additional info?
> I haven't put a ton of thought into
> this, but I'm hoping we can either (a) use debug info as is or add some
> extra (valid) debug info to support this, or (b) add an extra
> debug-info-like section to instrumented binaries with the information we
> need.
>
I'd try this data