Re: Issue 350 in address-sanitizer: LLVM sanitizer-bootstrap bot failing
Comment #1 on issue 350 by samso...@google.com: LLVM sanitizer-bootstrap bot failing https://code.google.com/p/address-sanitizer/issues/detail?id=350 Don't know. Maybe, instrumented binaries with debug info are just much larger, so linking them requires more memory. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 350 in address-sanitizer: LLVM sanitizer-bootstrap bot failing
Status: Accepted Owner: euge...@google.com CC: samso...@google.com Labels: Type-Defect Priority-Medium New issue 350 by euge...@google.com: LLVM sanitizer-bootstrap bot failing https://code.google.com/p/address-sanitizer/issues/detail?id=350 I see multiple ld processes, each takes from 1 to 4 Gb RAM (RSS). Heavy swapping (the machine has 24Gb RAM). No idea where this comes from. We don't instrument ld, and on my machine (non-bootstrap) ld takes ~300Mb for the same targets. One of the targets is clang-format. Any ideas? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Small improvements to run_spec_clang_asan.sh
Done.
On Wed, Oct 1, 2014 at 8:18 PM, Yuri Gribov wrote:
> Cool! Could someone apply this then?
>
> On Wed, Oct 1, 2014 at 2:18 PM, 'Evgeniy Stepanov' via
> address-sanitizer wrote:
>> Sorry, my bad, missed the "$" sign.
>>
>>
>> On Wed, Oct 1, 2014 at 2:03 PM, Yuri Gribov wrote:
>>> On Wed, Oct 1, 2014 at 1:56 PM, 'Evgeniy Stepanov' via
>>> address-sanitizer wrote:
> CLANGXX=${CLANGXX:-$(echo $CLANG | sed -e 's/gcc$/g++/')}
What if there is more than one "gcc" in the compiler path?
>>>
>>> Sorry, don't understand... I'm just replacing trailing gcc with g++ so
>>> e.g. path/to/my/cross-gcc becomes path/to/my/cross-g++.
>>>
>>> -Y
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "address-sanitizer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to address-sanitizer+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "address-sanitizer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to address-sanitizer+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
