Skip to content

Commit cf05e7d

Browse files
committed
VSCode integration isn't JLink specific anymore
1 parent d9ab19d commit cf05e7d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,12 +63,12 @@ When trying to step into the rust sources you may get an error that files with p
6363

6464
### VSCode Integration
6565

66-
The [Native Debug] extension can be used to debug Rust code directly in the editor. To use it you will need to add a launch configuration to your `.vscode/launch.json` file. Below is an example that connects to a Segger JLink server on port 2331. If you are using OpenOCD this port is most likely 3333.
66+
The [Native Debug] extension can be used to debug Rust code directly in the editor. To use it you will need to add a launch configuration to your `.vscode/launch.json` file. Below is an example that starts gdb and executes the commands specified in `debug.gdb`:
6767

6868
```
6969
"configurations": [
7070
{
71-
"name": "JLink Remote",
71+
"name": "Remote debug",
7272
"type": "gdb",
7373
"request": "launch",
7474
"cwd": "${workspaceRoot}",

0 commit comments

Comments
 (0)