Skip to content
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

Issues with resume/breakpoints and php adapter #11

Open
rchl opened this issue Nov 1, 2018 · 2 comments
Open

Issues with resume/breakpoints and php adapter #11

rchl opened this issue Nov 1, 2018 · 2 comments

Comments

@rchl
Copy link
Contributor

rchl commented Nov 1, 2018

  1. Debugger: Open
  2. Debugger: Start
  3. Place a breakpoint in the code
  4. Reload page

Expected: Breakpoint is hit and stack trace is visible.
Actual: Works as expected.

  1. Debugger: Resume
  2. Reload page again

Expected: Same as after 4 -- breakpoint is hit and stack trace is visible.
Actual: Stack trace shows the request but doesn't expand to show file names and it's not possible to navigate through stack frames.

Here are screenshot of what happens after 4 (correct) and after 6 (incorrect).

ok

fail

Not sure if the problem is in this package or adapter but it works fine in VSCode.

@rchl
Copy link
Contributor Author

rchl commented Apr 7, 2020

I can still reproduce in 0.2.4.

Only that when it fails to break the second time, the state is just as if it didn't break (but execution is still paused).

And this exception triggers when it fails to pause the second time:

Traceback (most recent call last):
  File "/Users/me/Library/Application Support/Sublime Text/Packages/Debugger/modules/core/sublime_event_loop.py", line 13, in __call__
    self.callback(*self.args)
  File "/Users/me/Library/Application Support/Sublime Text/Packages/Debugger/modules/dap/client.py", line 328, in _on_initialized
    self._on_initialized_future.set_result(None)
  File "/Users/me/Library/Application Support/Sublime Text/Packages/Debugger/modules/libs/asyncio/futures.py", line 348, in set_result
    raise InvalidStateError('{}: {!r}'.format(self._state, self))
Debugger.modules.libs.asyncio.futures.InvalidStateError: FINISHED: <Future finished result=None>

@daveleroy
Copy link
Owner

Is this still an issue? If so is there a small example project that shows the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants