[lld] r256309 - Fix two asan found bugs:

[Kostya Serebryany via llvm-commits]

On Wed, Jan 13, 2016 at 1:35 PM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:

> On 4 January 2016 at 13:33, Kostya Serebryany <kcc at google.com> wrote:
> > Cool!
> > I wonder if it makes sense to have a fuzzer for lld, similar to what we
> have
> > for clang and clang-format?
>
> Maybe, it probably depends on what we are fuzzing for.
>

Any kind of stability issues.
It's hard to limit the fuzzing to legal inputs (valid .o files), so most of
the fuzzed tests will be illegal and thus may touch various dusty corners
otherwise untouched by regular work flow.
Given that lld *probably* does not have much security surface, it may be a
waste of time to fix those dusty corners.
But that's still the simplest way to get the interesting stability bugs by
fuzzing.




>
> Broken .o files are really uncommon, unless one is working on a
> producer (MC). For lld itself we have so far been using a "don't
> crash" policy, but not much more. For example, we will produce garbage
> if given ABI invalid TLS relocations.
>
> Cheers,
> Rafael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160113/28da413b/attachment.html>