[root@localhost ~]# asterisk -vvvvvgc
FATAL: ThreadSanitizer can not mmap the shadow memory (something is mapped at 0x55a96afe6000 < 0x7cf000000000)
FATAL: Make sure to compile with -fPIE and to link with -pie.
[root@localhost ~]# gcc --version
gcc (GCC) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I have tried with version 18, Centos version 7.9, 7.7 but no luck at all. Could anyone help on this please.
Literally the message is saying that it is trying to place something in a particular memory range, but there is already something there. -fPIE causes shared libraries executables slightly bigger, but such that they don’t have to be loaded at a fixed address.
ThreadSanitizer is an optional debugging tool and has extended support status, which means it is only supported by the open source community, not by Sangoma’s Asterisk team.
continue on it…
I did some googling and found that Asterisk need libtsan.so.0.0.0 module to install and this module is for memory related stuff like ThreadSanitizer and ThreadAddress .
As i remove it then asterisk didn’t install and if I tried to run asterisk then Error is change. which means it’s somthing code level + Operating System dependent in Asterisk project.
I am not expert in C or C++ but it’s on the basis of googling…
Below is reference link for further details.
Have you disabled it in make menuconfig? Did you remove it using the OS package manager, and did you re-run configure after removing it. It is configure that checks what libraries are present, and the library checking may be, in part, based on indexes of libraries, rather than the libraries themselves.
I found the github section; that is how I knew it was a debugging tool.
Actually, I think cloudfare may have taken a disliking to your IP address, which seems to be an Indian mobile network… cloudfare is the company that seems to run most people’s web servers, these days, and I think they do have a significant false positive rate. One of the reasons I think they are used is that they are in a better position to survive a DDoS attack that individual small to medium sized sites.