Hi Jeff, I put a SIGILL handler in. Running normally without valgrind shows the signal is caught and ignored (when kill -ILL <pid> is sent)
But it seems that valgrind is disabling my signal handler. Running under valgrind still exits with > Valgrind will now raise a SIGILL signal which will probably kill your program. > Process terminating with default action of signal 4 (SIGILL) I'm not familiar with clang or the gcc sanitizers. Currently using g++ 4.4.7. Are they an option to find my memory leak? Valgrind looks like a dead end. Danny On 27/11/2016, at 12:04 PM, Jeffrey Walton wrote: > You can install a SIGILL handler to continue execution. I'm guessing > it will probably foul some Valgrind analysis. I don't know if it will > ruin all analysis. > > You might also retard your optimization level a bit so vectorizing > instructions are used less frequently. Valgrind recommends -O1 or -O0 > (http://valgrind.org/docs/manual/QuickStart.html), but I've noticed > GCC will utilize some vectorization even at -O1 level, like wide > memcpy's. Maybe a selection of -fno-XXX compiler options will ferret > the unwanted instructions. > > You can also use Clang or GCC's sanitizers. I try to test will all the > analysis tools I can get my hands on. In cases where Valgrind does not > run, I depend on other tools, like Coverity and Sanitizers.
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
