[PATCH] D30818: [lsan] Don't handle DTLS of thread under destruction
Maxim Ostapenko via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Wed Mar 22 14:20:14 PDT 2017
m.ostapenko added a comment.
In https://reviews.llvm.org/D30818#707959, @eugenis wrote:
> In https://reviews.llvm.org/D30818#706590, @m.ostapenko wrote:
>
> > After more debugging it seems that the issue is even more complicated.
> >
> > Tracer caught signal 11: addr=0x7fb108da4000 pc=0x423990 sp=0x7fb135ffed90
> > ...
> > 0x7fb1085a4000-**0x7fb108da4000** rw (0x000000000003)
> >
>
>
> This address does not look accessible to me. Well, that depends on the next mapping.
Oh, right, this is the highest address, not the lowest... Sorry. AFAIR on x86_64 static TLS (as well as TCB) for non-main threads should be located right above stack area (need to recheck).
Repository:
rL LLVM
https://reviews.llvm.org/D30818
More information about the llvm-commits
mailing list