Heap Tracing

App, Heap, System View Related Stuff

Here we will try to provide some info about how app/log/heap/system view tracing is implemented.

Communications

We completely rely on open-ocd for these features to work, we use tcl to communicate with the open-ocd running process and pass out the command to it.

Flow

• Check if open-ocd is running?
• If open-ocd is not running, present the user with UI to start the open-ocd process (please note the user don't really need the openocd to be run from within the vscode or even on the host system, as long as we can communicate to the http host running the tcl we can talk with the chip)
• On Successful Connection we get a connect even emitted on the TCL instance
• Then we can easily send command to the running open-ocd process via tcl, using the sendCommandWithCapture(command: string) method
• To get the response we have to register a response listener on TCL instance

Collecting & Saving Heap/Log Tracing Data

The data collected from the log and heap tracing is saved in the traces sub-directory of the project and they are saved in file name such that we can show UI based on the timestamp