mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
fbb2135214
MIRunControlEventProcessor_7_0. It also reverts CLIEventProcessor and MIRunControlEventProcessor to the logic needed for a GDB pre 7.0 (the way we released it in 1.0) MIThreadExited and MIThreadCreated events are now only issued once. Running events are also issued only once, however, it needed a little gymnastics to keep the same functionality. Before 7.0, what we did was trigger the event once a continue, step or next command was executed; this allowed to also know the type of command that caused the running event. With the new MI event "*running", we don't know the type of the command that caused it. What I did was, like before, when a continue, step, next command is issued, I store the type of the command, and once the *running event occurs, I use that type. I do this using a global MIRunControlEventProcessor_7_0.fLastRunningCmdType When issuing such a continue, etc command through the CLI, we still need to somehow remember the type of the command. This is under discussion in the bug. |
||
|---|---|---|
| .. | ||
| org.eclipse.dd.doc.dsf | ||
| org.eclipse.dd.dsf | ||
| org.eclipse.dd.dsf.debug | ||
| org.eclipse.dd.dsf.debug.ui | ||
| org.eclipse.dd.dsf.ui | ||
| org.eclipse.dd.examples.dsf | ||
| org.eclipse.dd.examples.pda | ||
| org.eclipse.dd.examples.pda.ui | ||
| org.eclipse.dd.gdb | ||
| org.eclipse.dd.gdb.launch | ||
| org.eclipse.dd.gdb.ui | ||
| org.eclipse.dd.mi | ||
| org.eclipse.dd.tests.dsf | ||
| org.eclipse.dd.tests.gdb | ||