Jonathan A. Sternberg dbda218489 dap: make exec shell persistent across the build ...

Invoking the shell will cause it to persist across the entire build and
to re-execute whenever the builder pauses at another location again.

This still requires using `exec` to launch the shell. Launching by frame
id is also removed since it no longer applies to this version.

Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>

2025-08-11 12:40:09 -05:00

..

common

dap: support stopOnEntry to configure behavior when starting the debugger

2025-07-07 09:39:23 -05:00

adapter_test.go

dap: support stopOnEntry to configure behavior when starting the debugger

2025-07-07 09:39:23 -05:00

adapter.go

dap: make exec shell persistent across the build

2025-08-11 12:40:09 -05:00

client_test.go

dap: add debug adapter implementation

2025-06-30 10:51:20 -05:00

config.go

dap: support stopOnEntry to configure behavior when starting the debugger

2025-07-07 09:39:23 -05:00

conn.go

dap: add debug adapter implementation

2025-06-30 10:51:20 -05:00

debug_shell.go

dap: make exec shell persistent across the build

2025-08-11 12:40:09 -05:00

eval.go

dap: make exec shell persistent across the build

2025-08-11 12:40:09 -05:00

handler.go

dap: support evaluate request to invoke a container

2025-07-15 10:45:25 -05:00

server.go

dap: support evaluate request to invoke a container

2025-07-15 10:45:25 -05:00

thread.go

dap: make exec shell persistent across the build

2025-08-11 12:40:09 -05:00

variables.go

dap: filesystem inspection when paused on a digest

2025-07-28 09:52:30 -05:00