Closed dkowis closed 11 years ago
A workaround for me was to put it into a class, and now I get epic butt-tons of debug information :D
This works fine for me: https://gist.github.com/jordansissel/5806284
Darn, stupid old ruby. I'll just keep using my class hack for now then.
Thanks :)
The problem is ruby 1.8's format for backtraces is different, it seems, than 1.9's.
Yay ruby :(
fixed by dca5cb7c5a6c5d70eac02baa8ed8d0607e605c26
cabin 0.6.1 released.
Thanks for supporting old rubies, and sorry that I'm still on old rubies
So if you do, you get a nasty exception:
Diagnosing with puts'es from a project of mine: This stems from the
BACKTRACE_RE
:BACKTRACE_RE: (?-mix:([^:]+):([0-9]+):in
(.*)')`The
callinfo
variable when used in a rake task is:CALLINFO: ./lib/tasks/packaging.rake:87
So yeah, that regexp doesn't match, and then it's all over :(