Stack trace error messages less useful on latest releases of Chrome

[anodos]

I recently updated to Chrome 38.0.2125.104 and Streamline stack traces have become less useful. Here is an example:

TypeError: Cannot read property 'Symbol(formatted stack trace)' of undefined
    at TypeError.stack (http://localhost:8080/js/bootstrap.js:20222:7294)
    at http://localhost:8080/js/compiled-templates/_core_event_1fcdcaa5abb9a00df84963a0c4348c5c.js:398:296
    at ___ (http://localhost:8080/js/bootstrap.js:20222:4157)

Specifically, before this version of Chrome the error message output the actual property name, whereas now it says, "Symbol(formatted stack trace)". I should note that we are using the callbacks version of the runtime.
I've narrowed the problem down to the way Streamline replaces the stack property. It attempts to get the existing 'stack' getter like so: var getter = e.__lookupGetter__("stack");
In the newest version of Chrome this does indeed return what appears to be a getter function, but then when the getter is executed in the replacement getter:

e.__defineGetter__("stack", function() {
  return formatStack(e, getter());
});

it returns this text: TypeError: Cannot read property 'Symbol(formatted stack trace)' of undefined
A workaround is to pass in the original Error object as 'this' to the getter:

e.__defineGetter__("stack", function() {
  return formatStack(e, getter.call(e));
});

That seems to do it in my version of Chrome anyway.

[bjouhier]

You nailed it. Can you submit the fix as a pull request?

[anodos]

I created a pull request (#243). Let me know if you need anything else.