Leo Chen.
2016-09-11 11:23:13 UTC
Hi, all
Normally, my programe use sigaction() to catch the signal SIGSEGV, to do
something about memory reserve/commit (such as mmap()/mprotect() ). The
signal of SIGSEGV is my expected behavior, and it just work fine.
But if I use Oprofile to profile my programe. My programe will abort
immediately and get this error message:
"profiled app killed by signal 11 (SIGSEGV)"
My question is: if I don't change my programe's implementation, how can I
set the Oprofile to ignore the signal SIGSEGV?
Normally, my programe use sigaction() to catch the signal SIGSEGV, to do
something about memory reserve/commit (such as mmap()/mprotect() ). The
signal of SIGSEGV is my expected behavior, and it just work fine.
But if I use Oprofile to profile my programe. My programe will abort
immediately and get this error message:
"profiled app killed by signal 11 (SIGSEGV)"
My question is: if I don't change my programe's implementation, how can I
set the Oprofile to ignore the signal SIGSEGV?