https://github.com/eclipse-cdt-cloud/cdt-amalgamator

https://github.com/eclipse-cdt-cloud/cdt-amalgamator

Last synced: 6 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/eclipse-cdt-cloud/cdt-amalgamator
• Owner: eclipse-cdt-cloud
• License: epl-2.0
• Created: 2022-01-20T19:01:24.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2024-04-22T23:23:33.000Z (almost 2 years ago)
• Last Synced: 2025-04-10T05:39:42.787Z (11 months ago)
• Language: TypeScript
• Size: 165 KB
• Stars: 2
• Watchers: 8
• Forks: 7
• Open Issues: 2
• Metadata Files:
  • Readme: readme.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Eclipse CDT Debug Adapter Amalgamator

This is a debug adapter that allows common control over multiple debug adapters simulataneously,

amalgamating their outputs to provide to VSCode a single Debug Adapter interface.

## Using the Amalgamator

The amalgamator is not published and can be run within a VS Code debug session.

-   Checkout this repository

-   Checkout https://github.com/eclipse-cdt/cdt-gdb-vscode

-   Add both repositories to a new VSCode workspace

-   Build both repositories (`yarn && yarn build`)

-   Build the sample application (`make -C sampleWorkspace`)

-   Launch the `Extension` launch configuration from `.vscode/launch.json`

-   Place a breakpoint on `empty1.c` and `empty2.c`

    -   These two files represent the two processes in a multi-process debug session

-   Update the paths to `cdt-gdb-adapter/dist/debugAdapter.js` in the sample workspace's `launch.json`

-   In the _Extension Development Host_ launch the `Amalgamator Example`

-   Debug the two processes, e.g.

    -   step the processes indpe

    -   observe variables in different processes

    -   examine memory with the memory browser (`Ctrl+Shift-P` -> _GDB: Open Memory Browser_)