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

No backtrace available for ArgumentError #525

Open
jochenseeber opened this issue Sep 1, 2023 · 0 comments
Open

No backtrace available for ArgumentError #525

jochenseeber opened this issue Sep 1, 2023 · 0 comments

Comments

@jochenseeber
Copy link

When using better_errors, I get no backtraces (and no REPL) for ArgumentError thrown from code. Forcing them with raise works fine.

I traced the problem back to set_backtrace not being called when the ArgumentError is caused by the code, but it is called when the error is forced with raise. The constructor is called in both instances

I saw some patch that added setting the backtrace to both the constructor and set_backtrace, but this code seems to be gone from the current release. Is there a reason for not patching the constructor any more?

Environment

  • better_errors: 20.10.1
  • binding_of_caller: 1.0.0
  • rails: 7.0.7.2
  • ruby: 3.2.2
  • arch: arm64 (Mac M1)
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

1 participant