Fix a problem where lldb-mi would not stop the debuggee after -exec-interrupt command.
authorHafiz Abid Qadeer <hafiz_abid@mentor.com>
Mon, 23 Feb 2015 18:27:17 +0000 (18:27 +0000)
committerHafiz Abid Qadeer <hafiz_abid@mentor.com>
Mon, 23 Feb 2015 18:27:17 +0000 (18:27 +0000)
commitcf0698987bff6ce3499f93912592d282b895b2b0
treedac7076d3dada9c1b16942d3efbc6ed6d1cf657e
parentff1b5c4244bd325104c40b7aba6b2d4d0749cbad
Fix a problem where lldb-mi would not stop the debuggee after -exec-interrupt command.

Summary:
This revision fixes a problem where lldb-mi would not stop the execution after exec-interrupt call.
On Linux, SIGSTOP is used to stop the debuggee process. LLDB stopped the debuggee alright. But when
lldb-mi received the notification of stopping with reason as SIGSTOP, it would resume the process.
This was heppening in CMICmnLLDBDebuggerHandleEvents::HandleProcessEventStopSignal. This function aslo
used hard coded numbers for signal istead of symbolic names.

This revision changes code to treat SIGSTOP reason as SIGINT. Also used symbolic names for signals
instead of numbers.

Reviewers: ki.stfu, clayborg

Reviewed By: ki.stfu, clayborg

Subscribers: zturner, lldb-commits

Differential Revision: http://reviews.llvm.org/D7783

llvm-svn: 230237
lldb/test/tools/lldb-mi/signal/TestMiSignal.py
lldb/tools/lldb-mi/MICmnLLDBDebuggerHandleEvents.cpp
lldb/tools/lldb-mi/MICmnLLDBDebuggerHandleEvents.h