llvm dev - Sep 2016 - -fsanitize=memory failing on 3.9.0

Please do the bisect, nice to hear it recently worked!

At this point I built mean with debug and its failing with initializing a
LFStack doing an atomic operation, IIRC.

On Sun, Sep 11, 2016, 9:09 AM Renato Golin <renato.golin at linaro.org>
wrote:
> On 7 September 2016 at 18:41, Wink Saville via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Further more, there is a bug reported concerning a seg  fault when
> > using msan on Arch Linux (https://bugs.archlinux.org/task/50385) so
> > I'm not the only person in the world have a problem.
>
> I'm having the same problem on trunk. The last time I did run the
> sanitizer tests was about a month or two ago, just before the release,
> and it was working well.
>
> A short bisect could tell us which commit broke it... I'll try
> something on my side.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160911/de5b173a/attachment.html>

On 11 September 2016 at 18:40, Wink Saville <wink at saville.com>
wrote:
> Please do the bisect, nice to hear it recently worked!
So, I went as far back as 3 months ago and it still crashes. I think
Reid is right that some environment change (kernel version?) made it
crash.

Best thing to do is to put all that info into LLVM bugzilla, link all
relevant information and go from there.

Unfortunately, I'm not an expert on either msan or x86, so it would be
good to include the rest of the sanitizer folks on the bug. If you
create one, copy me and I'll try to put all relevant people in.

cheers,
--renato

If you are on glibc-2.24, did you patch it with the fix
24e2b1cede1952d7d4411a3cafd25dd8593dab9f that revert commits
80f87443eed17838fe453f1f5406ccf5d3698c25 and
a824d609581d5ee7544aabcbbc70e8da44b2b5b6?  I had to do that since it
broke go, gcc, and clang address sanitizers without the patch.


On 9/12/16, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org>
wrote:
> On 11 September 2016 at 18:40, Wink Saville <wink at saville.com>
wrote:
>> Please do the bisect, nice to hear it recently worked!
>
> So, I went as far back as 3 months ago and it still crashes. I think
> Reid is right that some environment change (kernel version?) made it
> crash.
>
> Best thing to do is to put all that info into LLVM bugzilla, link all
> relevant information and go from there.
>
> Unfortunately, I'm not an expert on either msan or x86, so it would be
> good to include the rest of the sanitizer folks on the bug. If you
> create one, copy me and I'll try to put all relevant people in.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>