Repository navigation
Support "attach" stop reason #566
Description
Some debuggers suspend the execution after an attachment to a running program.
Sometimes this behavior is useful, other times it is more convenient to resume after attach automatically.
Please add the "attach" stop reason to the list of known values in the StoppedEvent.reason.
This will facilitate interaction between editors and debuggers and allow configuring the behavior on the DAP client side.
Activity
mfussenegger commentedon Oct 17, 2025
Many debug adapters already support a
stopOnEntryproperty that's part of the launch request to control if it should stop immediately. Couldn't this pattern be used forattachtoo?nd-work commentedon Oct 17, 2025
Oh, I didn't know about
stopOnEntry.I think the
attachstop reason can be useful on its own. For example, when a debugger doesn't allow to configure thestopOnEntrybehavior, it can still report the stop after attach.In my opinion it would be great to have both
stopOnEntryandattachstop reason in the spec to simplify coordination between clients and servers.connor4312 commentedon Oct 17, 2025
We have the stop reason
entrywhich is intended to be used for this purpose.nd-work commentedon Oct 17, 2025
Can
stopOnEntryget an official description in the spec?I believe debuggers will have more incentives to support it.
tromey commentedon Oct 17, 2025
It would be great if the meaning of these values was spelled out in the spec. I didn't know what this one meant when writing the gdb DAP implementation so I just ignored it...
connor4312 commentedon Oct 17, 2025
stopOnEntry is a common configuration value of various debug adapters, but this configuration is not in-scope for DAP.
👍