Skip to content

Backtrace in ArgumentError is wrong sometimes #3624

@auroranockert

Description

@auroranockert

This is on jruby 9.0.4.0 (2.2.2) 2015-11-12 b9fb7aa Java HotSpot(TM) 64-Bit Server VM 24.79-b02 on 1.7.0_79-b15 +jit [darwin-x86_64]

I can't say what exactly is wrong except that the last frame in the Ruby-only trace is wrong, or what is triggering it. My feeling is that the method name and arity message is correct, and that the last frame is just wrong filename/line number. But since it is inside ActiveRecord (which has internals I'm not confident with) I can't say for sure if anything else is wrong.

https://gist.github.com/jensnockert/078e74541c6d50989ce8

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions