Displaying 1 result from an estimated 1 matches for "num_live_dtl".
Did you mean:
num_live_dtls
2018 Feb 02
0
santizer problems with dynamic thread local storage
...it on an older system with glic 2.17 installed and turn on msan
debug verbosity to 2 I see this:
==100505==__tls_get_addr: DTLS_Resize 0x3fff9e1aebf0 0
==100505==__tls_get_addr: 0x3fff9e4dff38
{0x000000000003,0xffffffffffff8000} => 0x3fff9d8b0000; tls_beg:
0x3fff9d8b0000; sp: 0x3fff9e1ad740 num_live_dtls 1
==100505==__tls_get_addr: glibc <=2.18 suspected;
tls={0x3fff9d8b0000,0x000000100000}
stack: 0x3fff9e1ad950 dtls: 0x3fff9d8b0000
...etc... and the test works OK.
The == messages are from DTLS_on_tls_get_addr in
sanitizer_tls_get_addr.cc and show that it correctly deduced the glibc
version...