search for: reportsigsegv

...t of the failures are related with the fact the stack is not being dumped. I tried to understand what might be wrong and started by looking into the null_deref.cc test as it hangs during the test run. I observe that after the detection of the faulty memory access it receives a SEGV after entering ReportSIGSEGV() more precisely when it gets to the __intercept_strlen() and tries to access flags()->replace_str. The caller of __intercept_strlen() is get_cie_encoding() from libgcc (version 4.8.2 in my system). As I am not familiar with the sanitizer implementation, I was wondering if this is an expected...

...the stack is not being dumped. >> >> I tried to understand what might be wrong and started by looking into the >> null_deref.cc test as it hangs during the test run. I observe that after >> the detection of the faulty memory access it receives a SEGV after entering >> ReportSIGSEGV() more precisely when it gets to the __intercept_strlen() and >> tries to access flags()->replace_str. The caller of __intercept_strlen() is >> get_cie_encoding() from libgcc (version 4.8.2 in my system). >> >> As I am not familiar with the sanitizer implementation, I wa...

...> > >> I tried to understand what might be wrong and started by looking into > the > >> null_deref.cc test as it hangs during the test run. I observe that > after > >> the detection of the faulty memory access it receives a SEGV after > entering > >> ReportSIGSEGV() more precisely when it gets to the __intercept_strlen() > and > >> tries to access flags()->replace_str. The caller of > __intercept_strlen() is > >> get_cie_encoding() from libgcc (version 4.8.2 in my system). > >> > >> As I am not familiar with the...