Skip to content

Release v0.2.8

Latest
Compare
Choose a tag to compare
@ovidiuostoia ovidiuostoia released this 18 Dec 12:32
· 5 commits to main since this release
297fdd6

Visual Studio Code Target Communication Framework (TCF) Debugger Extension

This extension allows debugging via Target Communication Framework (TCF) from Visual Studio Code.

Manage breakpoints, resume after breakpoint hit, see the call stack and variables.

Requirements

No dependencies. The extension only requires Visual Studio Code.

Read the full manual or just follow the steps below.

Installation

Download and install the .VSIX file. (Note that if you download a .tgz file the
.vsix is probably inside the .tgz archive).

    File Edit Selection View Go Run Terminal Help
-────────────────────────────
 📃    Extensions   ↻ [···]  ⬅️ 1. Press here
 🔎                      ┌────────────────────────────┐
 🐞                      │Views                       │
|🧩                      │Check for Extension Updates │
 ⚙️                      ├────────────────────────────┤
 📺                      │Install from VSIX...        │ ⬅️2. Then here
 🏁                      └────────────────────────────┘

Configuration

A configuration of type tcf will auto-complete when you edit launch.json.

Note that the extension will connect to the TCF port so the debugged application must already be running (locally or remote) and the TCF port must be accessible. In practice you will have a local debugger running so you always connect to the local debugger TCF agent,
ie. to localhost.

Your local launch.json should work with the plain tcf configuration which connects by default to localhost:

"configurations": [
        {
            "type": "tcf",
            "request": "launch",
            "name": "Debug program"
        }
    ]

but you can also manually configure the following parameters (default values shown):

{
  "host": "127.0.0.1", // or any other hostname you want to connect to
  "port": 1534,  //or any other port where a TCF agent is listening

  "record": undefined, // use any file path here to write a log of all the TCF messages (useful for bug reports and playback)
  "playback": undefined, //use a pre-existing TCF recording to simulate a debugging session (this is obviously brittle and requires you to run close to the same commands)

  "timeout": 10000 //debug commands timeout in milliseconds (this may be useful for connection to very slow machines)

  "debugTCFMessages": false //toggle to true to see in the debug console the TCF messages being sent / received (for internal use generally)

  "type": "tcf",
  "request": "launch",
  "name": "Debug program"
}

Release Notes

0.2.8

  • Fix source file not found when TCFCodeAreaLineNumbers.File has absolute path
  • Maintenance