This repository has been archived by the owner on Jul 22, 2020. It is now read-only.
runner.faq
Klemens Morgenstern edited this page Apr 4, 2018
·
2 revisions
Semihosting is a feature in many embedded development toolsets, that allows stubbing for the syscalls similar to what we described in a prior section.
The main problem is that semihosting is provided by the gdb-server, e.g. openocd or st-link, and the console output can be written into the stdout
/ stderr
stream of the server.
The debug-runner does not capture that, to keep the logs seperate, thus semihosting output will not be received in the the gdb-output. In addition,
out solution will run faster, because it uses a small buffer.
For more information on semihosting see
- Overview
- Runner Introduction
- Runner Invocation
- Runner Plugins
- Runner Extender
- Runner FAQ
- Runner Reference
- Unit Introduction
- Unit Tutorial
- Unit FAQ
- Unit Reference
- Calltrace Introduction
- Calltrace Tutorial
- Calltrace FAQ
- Calltrace Plugin
- Calltrace Reference
- Serial Introduction
- Serial Tutorial
- Serial Invocation
- Serial Reference