All Projects → probe-rs → vscode

probe-rs / vscode

Licence: other
VSCode debug extension for probe-rs. It uses the MS DAP protocol to communicate directly with the probe (via probe-rs), and supports basic command line debugging in addition to VSCode UI.

Programming Languages

typescript
32286 projects

Projects that are alternatives of or similar to vscode

Acho
The Hackable Log
Stars: ✭ 189 (+320%)
Mutual labels:  debug
Gulp Debug
Debug Vinyl file streams to see what files are run through your Gulp pipeline
Stars: ✭ 223 (+395.56%)
Mutual labels:  debug
Gulp Strip Debug
Strip console, alert, and debugger statements from JavaScript code
Stars: ✭ 242 (+437.78%)
Mutual labels:  debug
The Front End Knowledge You May Not Know
😇 你可能不知道的前端知识点
Stars: ✭ 2,238 (+4873.33%)
Mutual labels:  debug
Bugsnag Ruby
Bugsnag error monitoring & reporting software for rails, sinatra, rack and ruby
Stars: ✭ 211 (+368.89%)
Mutual labels:  debug
Kint
Kint - a powerful and modern PHP debugging tool.
Stars: ✭ 2,582 (+5637.78%)
Mutual labels:  debug
Kinovision
Frame visualization utility for Unity
Stars: ✭ 177 (+293.33%)
Mutual labels:  debug
fastapi-debug-toolbar
A debug toolbar for FastAPI.
Stars: ✭ 90 (+100%)
Mutual labels:  debug
Iosdebugdatabase
make it easy to debug databases in iOS applications iOS debug database
Stars: ✭ 219 (+386.67%)
Mutual labels:  debug
Cli Debugging Cheatsheets
🔥 Collection of command-line debugging cheatsheets for multiple languages and runtimes
Stars: ✭ 239 (+431.11%)
Mutual labels:  debug
Magicshader
🔮 Tiny helper for three.js to debug and write shaders
Stars: ✭ 205 (+355.56%)
Mutual labels:  debug
Icecream
🍦 Never use print() to debug again.
Stars: ✭ 5,601 (+12346.67%)
Mutual labels:  debug
Pysnooper
Never use print for debugging again
Stars: ✭ 14,815 (+32822.22%)
Mutual labels:  debug
Logcat
Android 日志打印框架,在手机上可以直接看到 Logcat 日志啦
Stars: ✭ 189 (+320%)
Mutual labels:  debug
awaitwhat
Await, What?
Stars: ✭ 48 (+6.67%)
Mutual labels:  debug
Laravel Migrate Fresh
An artisan command to build up a database from scratch
Stars: ✭ 179 (+297.78%)
Mutual labels:  debug
Icecream Cpp
🍦 Never use cout/printf to debug again
Stars: ✭ 225 (+400%)
Mutual labels:  debug
UnityCLI
Unity TCP CLI communication for debugging
Stars: ✭ 22 (-51.11%)
Mutual labels:  debug
alog
Update: use loguru instead. Simple straight logging your Python code
Stars: ✭ 38 (-15.56%)
Mutual labels:  debug
Simple Pt
Simple Intel CPU processor tracing on Linux
Stars: ✭ 232 (+415.56%)
Mutual labels:  debug

VS Code probe-rs-debugger

Documentation

Full documentation on Installation, Configuration and supported functionality can be found at the probe-rs webpage and under the visual tour heading

Development Setup - only applies if you want to contribute to the extension

To work on this extensions, you first need to install VS Code and nodejs. Afterwards, follow the following steps:

  • Checkout this repository

  • Inside the repository, install the prerequisites:

    npm install
    
  • Install the extensions VS Code recommends. If you prefer to do this manually, you can find the list of recommended extensions in the repository's `.vscode/settings.json' file. These can then be installed from the command line, for example:

    code --install-extension amodio.tsl-problem-matcher
    
  • Open VS Code

  • Press F5 to start a new VS Code instance where the extension can be debugged. You can also open the "Run and Debug" panel in the left sidebar, and then start the "Extension" debug configuration.

To run against a compiled executable of probe-rs-debugger

  • Press F5 to build and launch executable probe-rs-debugger. VSCode will open another VS Code window, titled [Extension Development Host].
  • In this new VSCode window,
    • Open an existing project, or create a new one.
    • In your project, configure the launch.json in your project, as per the minimum configuration example.
    • Select the debug environment you just created.
      • Press F5 to start debugging.

To run against a debuggable instance of probe-rs-debugger

  • Clone the probe-rs repository, and open it in VSCode.
    • In this probe-rs repo, select the debug environment DAP-Server probe-rs-debugger
    • Press F5 to start probe-rs-debugger as a debuggable server.
  • Switch to the VSCode instance of the probe-rs vscode repository.
  • In this new VSCode window,
    • Open an existing project, or create a new one.
    • In your project, configure the launch.json in your project, as per the existing debugger server example.
    • Select the debug environment you just created.
      • Press F5 to start debugging.

Build the extension

Building the extension refers to the process that generates the installable .vsix package.

  • Follow the instructions to setup your development environment.

  • In a terminal window, execute the following command:

    npm run package
    
  • This will generate a .vsix file in the root of the repository

Releasing the extension

  • The extension can only be released as part of the CI process on GitHub Actions.
  • The CI process is defined in .github/publish.yml.
  • Whenever a PR is merged, The CI process will also automatically build the extension, and:
    • If the version number was bumped in package.json, it will publish the extension to the VSCode Marketplace.
    • If the version number was not bumped, no publishing will occur.

Contributing

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed, without any additional terms or conditions, according to:

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].