-
Notifications
You must be signed in to change notification settings - Fork 196
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
Debugger crashes when frame no longer exists #452
Labels
bug
Something isn't working
Comments
2 tasks
lukaszsamson
added a commit
that referenced
this issue
Jan 10, 2021
…thread, frame and variable ids Fixes #452
lukaszsamson
added a commit
that referenced
this issue
Jan 10, 2021
…thread, frame and variable ids Fixes #452
axelson
pushed a commit
that referenced
this issue
Jan 14, 2021
* remove legacy io_request handlers we don't support OTP < R15B * rescue MatchError in :int calls Fixes #455 * make output device better conform to erlang I/O protocol see https://erlang.org/doc/apps/stdlib/io_protocol.html for details * return WireProtocol.send error to the caller no need to IO.warn if write fails * we are redirection stderr to stdout, use stdout as underlying device * inspect error * monitor debugged processes add test for mix task exit Fixes #454 * avoid debugger crashes when handling requests for no longer existing thread, frame and variable ids Fixes #452 * add test * forbid changes of underlying device opts * refactor and add tests coverage to invalid requests * Map.pop! is available since elixir 1.10 * run formatter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extracted from #451
Environment
Logs
If I now set a breakpoing to page_controller.ex at line 5 and I visit the page with a browser, the debugger stops at that line, but if I wait more or less one minute the debugger process crashes. This is the log:
The crash happens in
elixir-ls/apps/elixir_ls_debugger/lib/debugger/server.ex
Line 291 in 3acc1fd
Most likely a timeout in cowboy http request handler is killing the debugged process, which is not properly handled.
The text was updated successfully, but these errors were encountered: