| Summary: |
[non-stop][multi-process] No need to interrupt the inferior in non-stop mode |
| Product: |
[Tools] CDT
|
Reporter: |
Marc Khouzam <marc.khouzam> |
| Component: |
cdt-debug-dsf-gdb | Assignee: |
Marc Khouzam <marc.khouzam> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Marc Khouzam <marc.khouzam> |
| Severity: |
normal
|
|
|
| Priority: |
P3
|
CC: |
cdtdoug, ling.5.wang, pawel.1.piech
|
| Version: |
8.0 | Flags: |
marc.khouzam:
review?
(ling.5.wang)
|
| Target Milestone: |
8.0 | |
|
| Hardware: |
PC | |
|
| OS: |
Linux | |
|
| Whiteboard: |
|
| Attachments: |
| Description |
Flags |
|
Fix
|
marc.khouzam:
iplog-
|
|
Created attachment 190510 [details] Fix When we want to terminate the inferior or GDB, we send 'kill' or '-gdb-exit' respectively. However, we first check if MIInferiorProcess is RUNNING and if it is, we interrupt it so that GDB will accept commands. This behavior is specific to all-stop mode, where GDB does not accept commands when the inferior is running. In non-stop mode, GDB always accepts commands so we don't need to interrupt the inferior. Although this is not a big deal, it is valuable to handle MIInferiorProcess better for multi-process. This patch creates IMIRunControl#isTargetAcceptingCommands() instead of relying on MIInferiorProcess.