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

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
>

On 12 September 2016 at 07:11, Somchai Smythe
<buraphalinuxserver at gmail.com> wrote:
> 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.
I didn't. Shouldn't the arch glibc maintainer do that and push an
update?

The bug https://bugs.archlinux.org/task/50385 doesn't seem to be
associated with the glibc package...

--renato

On 12 September 2016 at 09:38, Renato Golin <renato.golin at linaro.org>
wrote:
> On 12 September 2016 at 07:11, Somchai Smythe
> <buraphalinuxserver at gmail.com> wrote:
>> 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.
>
> I didn't. Shouldn't the arch glibc maintainer do that and push an
update?
>
> The bug https://bugs.archlinux.org/task/50385 doesn't seem to be
> associated with the glibc package...
Open Mandriva seems to have a similar problem with glibc-2.24,
seg-faulting on MSAN's Linux/forkpty.cc.

Bero, have you reverted the patch mentioned above from glibc? If
reverting that works, we probably need to ask Arch folks to do the
same.

cheers,
--renato

I've looked at the version of libc I have and its 2.24:
$ /lib/libc.so.6
GNU C Library (GNU libc) stable release version 2.24, by Roland McGrath et al.

I then cloned the gcc 2.24 sources as of today and the code that
24e2b1cede1952d7d4411a3cafd25dd8593dab9f reverts is still there. I
also took a quick look at the Arch Linux glibc package
(https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/glibc)
and don't see any local patches.

Therefore I assume it hasn't been patched.



On Mon, Sep 12, 2016 at 1:38 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 12 September 2016 at 07:11, Somchai Smythe
> <buraphalinuxserver at gmail.com> wrote:
>> 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.
>
> I didn't. Shouldn't the arch glibc maintainer do that and push an
update?
>
> The bug https://bugs.archlinux.org/task/50385 doesn't seem to be
> associated with the glibc package...
>
> --renato