-
Notifications
You must be signed in to change notification settings - Fork 54
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
Nesting error and Crash When Debugging #65
Comments
Ah, I see. I will workaround into debug.gem but not sure it solves the issue. If you can, could you try this patch? diff --git a/lib/debug/thread_client.rb b/lib/debug/thread_client.rb
index 5f2d100..0a0cb00 100644
--- a/lib/debug/thread_client.rb
+++ b/lib/debug/thread_client.rb
@@ -568,7 +568,7 @@ module DEBUGGER__
unless only_self
s.ancestors.each{|c| break if c == Object; cs[c] = :ancestors}
if b = current_frame&.binding
- b.eval('Module.nesting').each{|c| cs[c] = :nesting unless cs.has_key? c}
+ b.eval('::Module.nesting').each{|c| cs[c] = :nesting unless cs.has_key? c}
end
end
|
Edit: Was apparently working but then hit the issue again with the patch. Here is the stack trace:
|
ko1
added a commit
to ruby/debug
that referenced
this issue
Oct 24, 2022
This will fix ruby/vscode-rdbg#65
Thank you above PR will fix this issue. |
ko1
added a commit
to ruby/debug
that referenced
this issue
Oct 24, 2022
This will fix ruby/vscode-rdbg#65
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seem to keep getting this nesting error after I leave the debugger idle for too long:
Any reason this might be occurring?
The text was updated successfully, but these errors were encountered: