In PCEventHandler::shouldStopForSignal(), SIGINT is not a stopping
signal. SIGINT's default action is to terminate the process, but it can
also be handled or ignored. It never stops, to my knowledge.
It's hard for me to know the original author's intent, but the other
match on SIGSTOP does make sense. SIGTSTP, SIGTTIN, and SIGTTOU are
also stopping signals, FWIW, but those may still be caught or ignored.
---
dyninstAPI/src/unix.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dyninstAPI/src/unix.C b/dyninstAPI/src/unix.C
index b681daf..ef06e01 100644
--- a/dyninstAPI/src/unix.C
+++ b/dyninstAPI/src/unix.C
@@ -193,7 +193,7 @@ bool PCProcess::instrumentMTFuncs() {
}
bool PCEventHandler::shouldStopForSignal(int signal) {
- if( signal == SIGSTOP || signal == SIGINT ) return true;
+ if( signal == SIGSTOP ) return true;
return false;
}
--
1.8.2.1
|