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

ruby-debug cannot show backtrace in certain instances #2367

Open
headius opened this issue Dec 29, 2014 · 2 comments
Open

ruby-debug cannot show backtrace in certain instances #2367

headius opened this issue Dec 29, 2014 · 2 comments

Comments

@headius
Copy link
Member

@headius headius commented Dec 29, 2014

From http://jira.codehaus.org/browse/JRUBY-6355

jruby --debug spec_example.rb

https://gist.github.com/1634453

(rdb:1) c

(rdb:1) bt
--> INTERNAL ERROR!!! org.jruby.runtime.DynamicScope.getEvalScope()Lorg/jruby/runtime/DynamicScope;
        org.jruby.debug.Context.contextCopyLocals(Context.java:407)
        org.jruby.debug.Context.frame_locals(Context.java:284)
...

I imagine this isn't expected.

@jrochkind
Copy link

@jrochkind jrochkind commented Feb 23, 2015

any ideas what's up with this? I'm running into it too, trying to use ruby-debug, I actually get it just trying to step through my code with next, not explicitly doing a bt. Which of course is making it hard to debug what I'm really trying to debug!

@marktriggs
Copy link
Contributor

@marktriggs marktriggs commented Jun 27, 2015

I hit this too. The full exception was:

 java.lang.NoSuchMethodError: org.jruby.runtime.DynamicScope.getEvalScope()Lorg/jruby/runtime/DynamicScope;

I'm not totally sure of the history here, but it seems like DynamicScope.getEvalScope() must have changed cardinality at some point in the past. In the latest version of jruby-debug there's some code to determine whether the runtime parameter is needed or not:

https://github.com/jruby/jruby-debug/blob/master/src/org/jruby/debug/Context.java#L414

Explicitly pulling in version 0.10.5.rc9-java of ruby-debug-base fixed this particular issue locally for me (previously I'd been running 0.10.4)

Cheers,
Mark

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

No branches or pull requests

3 participants