Wink Saville via llvm-dev
2016-Sep-12 21:02 UTC
[llvm-dev] -fsanitize=memory failing on 3.9.0
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
Renato Golin via llvm-dev
2016-Sep-12 21:08 UTC
[llvm-dev] -fsanitize=memory failing on 3.9.0
On 12 September 2016 at 22:02, Wink Saville <wink at saville.com> wrote:> 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.Right, I'm not expecting glibc itself to be patched by now, but if this impacts Arch and Open Mandriva, then both should revert locally, at least until it's fixed upstream. I also didn't see any patch on the Arch and I'm not sure how to contact the packager. Can you reply on the bug you opened about the (slight) progress we're making? Ask someone to try reverting the patch? I don't have a chroot just for that and I don't want to mess up my environment. :) cheers, --renato
Wink Saville via llvm-dev
2016-Sep-13 01:38 UTC
[llvm-dev] -fsanitize=memory failing on 3.9.0
I've updated the arch linux bug (https://bugs.archlinux.org/task/50385) with a patch for glibc in the arch linux packages that does fix the segment fault for me. On Mon, Sep 12, 2016 at 2:08 PM, Renato Golin <renato.golin at linaro.org> wrote:> On 12 September 2016 at 22:02, Wink Saville <wink at saville.com> wrote: >> 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. > > Right, I'm not expecting glibc itself to be patched by now, but if > this impacts Arch and Open Mandriva, then both should revert locally, > at least until it's fixed upstream. > > I also didn't see any patch on the Arch and I'm not sure how to > contact the packager. > > Can you reply on the bug you opened about the (slight) progress we're > making? Ask someone to try reverting the patch? I don't have a chroot > just for that and I don't want to mess up my environment. :) > > cheers, > --renato