title: Does the execution have to keep stopping to set a breakpoint?
body: <ol>
  <li>vscode@1.60.0</li>
  <li>vscode-go@v0.27.2</li>
  <li>go:1.16.3 darwin/amd64</li>
  </ol>
  <p>Hello I am developing api with gin.</p>
  <p>Whenever I add a breakpoint to the http handler, a <code>Execution halted to set breakpoints - please resume execution manually</code> is being output to the debug console.</p>
  <p>When developing an API, it is quite common to check breakpoints in handlers.
  Because you can see how the request came and the logic behaved and responded as intended.</p>
  <p>But every time I check and uncheck a breakpoint, I have to mechanically press Continue Debug.
  This greatly reduces development productivity.</p>
  <p>It didn't happen before, but it seems to be happening with a recent update.
  Is this the intended behavior?</p>
  <h4>Additional confirmed points</h4>
  <p>I was able to figure out what was causing the above issue by checking the release notes.</p>
  <p>The <code>dlv-dap</code> added in <a href="https://github.com/golang/vscode-go/releases/tag/v0.27.0" rel="nofollow noreferrer">Release 0.27.0</a> is identified as the cause of the problem. Using the <a href="https://github.com/golang/vscode-go/blob/master/docs/debugging-legacy.md#selecting-legacy-debug-adapter" rel="nofollow noreferrer">legacy debug adapter</a> does not cause the above problem.</p>
  <p>I can't seem to see what was raised above for known issues with dlv-dap. Is this behavior normal? Or is it still in development?</p>