Backtraces

[Elliot Winkler]

The lack of information when Johnson spits out a backtrace is
completely maddening:

Johnson::Error in 'Feature: Gift this (under Javascript) Scenario:
Choosing to gift items and going forward'
b is null
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/static.js:1218
[JavaScript]
inline:2302 [JavaScript]
inline:431 [JavaScript]
inline:139 [JavaScript]
inline:392 [JavaScript]
inline:5523 [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2193
[JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2191:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/env.js:2324:in
`__dispatchEvent__' [JavaScript]
/Library/Ruby/Gems/1.8/gems/envjs-0.3.6/lib/envjs/static.js:1718
[JavaScript]
/Library/Ruby/Gems/1.8/gems/johnson-2.0.0.pre3/lib/johnson/
ruby_land_proxy.rb:110:in `method_missing'
....

(Ignore the top line of the backtrace, I think that's envjs's doing...
it's the "inline's" I'm concerned about.) I'm going to wager a guess
that "inline" refers to an anonymous function inside some file. Is
there any way to retrieve which file that function was executed inside
of?? Debugging stuff like this is really frustrating and can easily
become a time sink...

-- Elliot

[Steven Parkes]

> The lack of information when Johnson spits out a backtrace is
> completely maddening

This is actually more an envjs issue than a Johnson issue. Johnson provides enough hooks to pass a string that SpiderMonkey will use in backtraces, it's just not hooked up in envjs for cases where the source is a URI (even a file URI, I think).

Could you submit an issue at http://github.com/smparkes/env-js? I can probably hack something into the current Johnson port and it's probably something that should go into the envjs platform API going forward ...