Displaying 5 results from an estimated 5 matches for "50385".
Did you mean:
0385
2016 Sep 12
3
-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 Sep 13
2
-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...
2016 Sep 12
2
-fsanitize=memory failing on 3.9.0
...c25 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
2016 Sep 07
2
-fsanitize=memory failing on 3.9.0
....module_ctor ()
#16 0x0000000000485c3d in __libc_csu_init ()
#17 0x00007ffff6f18220 in __libc_start_main () from /usr/lib/libc.so.6
#18 0x0000000000418b4a in _start ()
(gdb)
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.
Any suggestions on what the problem might be?
2016 Sep 11
2
-fsanitize=memory failing on 3.9.0
...lin <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 whi...