-
-
Notifications
You must be signed in to change notification settings - Fork 330
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
Issue with caller output in byebug >= 7.0.0 #188
Comments
Yep, this can be considered a bug. It was introduced together with #184. Notice thought that you can get the stack with the |
deivid-rodriguez
pushed a commit
that referenced
this issue
Nov 11, 2015
Don't eval things in a different thread unless using a new `debug` command.
@Aqualon Try last master and check if this is fixed, please. |
@deivid-rodriguez I checked it and the |
@Aqualon You're welcome, thanks for checking! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I found an issue with the output of caller in byebug >= 7.0.0.
I added byebug in a model and then executed a spec testing this model. On the breakpoint I called
caller
and got the complete stack with byebug 6.0.2 (I removed my home path from the output).To me that's helpful to follow the codepath that led to a certain place.
In byebug >= 7.0.0 I only get output of byebug's own
eval.rb
which for me is not really useful.Is this a bug or do I have to do something differently in byebug 7.0.0 and above to get the complete callstack? Also tried latest 8.1.0 and this version shows the same.
The text was updated successfully, but these errors were encountered: