printStackTrace throws exception when called from "use strict" code

[jphaas]

In strict mode, use of argument.caller throws an exception. This means that if there is strict mode code anywhere in the call stack, printStackTrace fails. Here's a jsfiddle that illustrates this: http://jsfiddle.net/SVN4D/ (I'm passing an integer as the error object to force IE-style stacktrace generation, since the implementation for webkit et al doesn't rely on argument.caller).

Instead of throwing an exception, I think it would make more sense to return as much of the call stack as we can, and then have the last entry in the array be something like 'error: cannot read strict mode stacktraces for this browser' or something.

[jontro]

In firefox when catching an exception in strict mode the exception object does not contain a stack trace. stacktrace.js does not detect firefox due to this and goes on to use the "other" function.

We had to add a try and catch around curr.caller to suppress the error to at least get a meaningful message and description.

try {
     curr = curr.caller;
}
catch (e) {
     break;
}

[jontro]

Actually it appears that for certain exceptions firefox will give no trace.
See http://jsfiddle.net/pdrnE/4/ for an example.

[victor-homyakov]

@jphaas http://jsfiddle.net/SVN4D/1/ works for me in Chrome 31 - retrieves partial stack up to works without exceptions, fails only in Firefox.

[victor-homyakov]

@jontro DOMException in Firefox and IE10 does not have stack (in Chrome and Opera 12 it has). In this case call stack will be traced from call chain (arguments.caller).

[SunboX]

+1 👍

[victor-homyakov]

Fix is ready. Will push it at weekend.

[eriwen]

👍 Thanks @victor-homyakov