MrHate updated this revision to Diff 248784.
MrHate added a comment.
Added a test case where test "process signal" without a running process.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D75418/new/
https://reviews.llvm.org/D75418
Files:
lldb/source/Commands/CommandObjectProcess.cpp
MrHate updated this revision to Diff 248088.
MrHate edited the summary of this revision.
MrHate added a comment.
Removed individual execution context updating.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D75418/new/
https://reviews.llvm.org/D75418
Files:
lldb/source/Commands/Command
MrHate updated this revision to Diff 247786.
MrHate added a comment.
removed unnecessary assignment in test
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D75418/new/
https://reviews.llvm.org/D75418
Files:
lldb/source/Commands/CommandObjectProcess.cpp
lldb/test/API/functionalities/co
MrHate updated this revision to Diff 247785.
MrHate added a comment.
Update the current execution context, then get signals from the current process.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D75418/new/
https://reviews.llvm.org/D75418
Files:
lldb/source/Commands/CommandObjectProc
MrHate added a comment.
Thanks for pointing out my misunderstanding on the Unix signals, and fetching
the list of valid signals from backend is always a better way indeed.
However, getting the current process from the current context `m_exe_ctx` which
is got from `m_interpreter` will cause an is