Skip to content

dap: add stack traces to stopped threads #3260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

jsternberg
Copy link
Collaborator

@jsternberg jsternberg commented Jun 18, 2025

Stack traces show the first parent of each operation that was run to
get to the current location. It shows either their custom name from the
LLB or it will show the command name.

stack-trace-example

Adds a simple implementation of the debug adapter that supports the very
basics of a debug adapter.

It supports the launch request, the configuration done request, the
creation of threads, stopping, resuming, and disconnecting from server.

It does not support custom breakpoints, stack traces, or variable
inspection yet. These are planned to be added in the future. It also
does not support sending output through the debug adapter yet.

Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
Stack traces show the first parent of each operation that was run to
get to the current location. It shows either their custom name from the
LLB or it will show the command name.

Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
@jsternberg
Copy link
Collaborator Author

Parts of this have been integrated with #3279. I'm going to close this as that other PR is more complete.

@jsternberg jsternberg closed this Jul 1, 2025
@jsternberg jsternberg deleted the dap-stacktrace branch July 1, 2025 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant