Context currently active.
((id, start, stop)*) Tells which breakpoints (identified by their id) are set for the space object. start and stop specifies the interval for the breakpoint.
Preferred gdb-remote variant.
Symbol table for the context.
| finish-function | finish the current function |
| info | print information about the device |
| next-instruction | run to the next instruction, skipping subroutine calls |
| next-line | run to the next source line, skipping subroutine calls |
| off | switch off context object |
| on | switch on context object |
| reverse-next-instruction | back to the previous instruction, skipping subroutine calls |
| reverse-next-line | back to the previous source line, skipping subroutine calls |
| reverse-step-instruction | back to the previous instruction |
| reverse-step-line | back to the previous source line |
| reverse-until-active | reverse until context becomes active |
| run-until-active | run until context becomes active |
| status | print status of the device |
| step-instruction | run to the next instruction |
| step-line | run to the next source line |
| symtable | set the symbol table of a context |
| uncall-function | go back to when the current function was called |
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.
next-line causes the simulation to run until it reaches another source line, but will not stop in subroutine calls. reverse-next-line is the same as next-line, except for running backwards. next-instruction and reverse-next-instruction are like next-line and reverse-next-line, respectively, except for stepping just one instruction instead of an entire source line.
finish-function causes the simulation to run until the current function has returned. uncall-function causes the simulation to run backwards until just before the current function was called.
These commands can either be called as context namespace commands, e.g., context.step-line, in which case the command will apply to that context; or not, e.g., step-line, in which case the command will operate on the current context of the current processor.