In IE and window.onerror, stack trace is uninformative about stacktrace.js HOT 8 CLOSED

Ahh...
I now know that I need to run this in http method, so the stack trace seems a little changed, but still not accurate.
I run the second case in http method, and got:
In IE:
{anonymous}(null)
printStackTrace()
{anonymous}("Object expected","http://localhost/javascriptStackTrace/testcase1.html",17)
bar(1)
bar(1)
bar(1)
bar(1)
bar(1)
bar(1)
bar(1)

In FF:

(?)()@http://localhost/javascriptStackTrace/stacktrace.js:74
run(null)@http://localhost/javascriptStackTrace/stacktrace.js:72
printStackTrace()@http://localhost/javascriptStackTrace/stacktrace.js:58
onerror("abc is not defined","http://localhost/javascriptStackTrace/testcase1.html",17)@http://localhost/javascriptStackTrace/testcase1.html:8

Both of the results are not expected, is there any missing in using your library?

Thanks!

from stacktrace.js.

Joe: I'm looking at this.

Note that there is a bug in the IE implementation when we lose the stack if you use recursion. This is because a construct that I need is overwritten and I cannot get it back.

Regardless, this is not your fault. Your Firefox results for the test are definitely wrong using window.onerror. Stay tuned!

from stacktrace.js.

Hi, I implemented this script, used in IE9 and I found some error (maybe I did something wrong). This is the ex:

So, when the clicked function is called (by an anchor or w/e), the error occurs, the window.error is triggered and the handler is called.
So, printStrackTrace is called and the magic of the script happens, but there is an issue, some how in this part:
while (curr && stack.length < maxStackSize) {
fn = fnRE.test(curr.toString()) ? RegExp.$1 || ANON : ANON;
args = Array.prototype.slice.call(curr['arguments']);
stack[j++] = fn + '(' + this.stringifyArguments(args) + ')';
curr = curr.caller;
}
the curr['arguments'] is null so the Array.prototype.slice.call() fails and everything else stop working.
I managed to fix this by updating this the condition: while (curr && curr['arguments'] && stack.length < maxStackSize)
but I am not an expert on JS, so I wouldn't know if this condition it's good enough or not.
I found that the issue only happens in IE9. In IE 6/7/8 everything works fine, but in IE9 the force error of the script is not getting into the stack (unlike other browsers). Any thoughts? Any advice so I can hack the code a little bit to make it work in all browsers again (sadly I need IE9)
Thanks

from stacktrace.js.

@lpena Yep, that would be good way to fix the error you are seeing.

I would recommend that you do not use printStackTrace() within window.onerror until we have implemented a better way to handle it. Follow this issue and #26 for updates.

from stacktrace.js.

subscribe

from stacktrace.js.

Subscribe

from stacktrace.js.

subscribe

from stacktrace.js.

Closing in favor of #96.

from stacktrace.js.