Comments on: Javascript Stacktrace update

By: arguments…callee…caller…

arguments…callee…caller… — Thu, 24 Jun 2010 11:27:07 +0000

[...] at generating a stack trace in JavaScript for the purpose of error reporting. There are plenty of existing projects out there that solve this problem, so I wouldn’t recommend rolling your [...]

By: Luke Venediger

Luke Venediger — Thu, 27 May 2010 13:46:50 +0000

Thanks for this Eric!

By: arguments…callee…caller… « Clever Title Coming Soon

arguments…callee…caller… « Clever Title Coming Soon — Tue, 04 May 2010 02:18:02 +0000

By: Eric Wendelin

Eric Wendelin — Sat, 24 Apr 2010 16:23:05 +0000

That is a great idea!

I’ve committed initial parts to the project and I’ll make updates so there is an interface to interact with.

Thanks!

By: DrSoong

DrSoong — Thu, 22 Apr 2010 06:36:13 +0000

Can you also make this great functionality available as a bookmarklet? That would really make it very useable, because you would not need to change the sourcecode on the website.

By: P

Wed, 03 Mar 2010 09:14:33 +0000

Opera 10.50′s stack trace in dragonfly is the most impressive i’ve seen, where most quit at the first closure or anonymous, it manages to go all the way down to the root.

By: 2ni

2ni — Wed, 24 Feb 2010 16:13:00 +0000

Any idea how this works with jquery?
I have
jQuery(document).ready( function () { foo['bar']++; });

and window.onerror = function(msg, url, line) {alert(printStackTrace());}

But the ready() function seems to swallow the stacktrace…
Any clue?

By: Sigue la traza de tus script con printStackTrace() | aNieto2K

Sigue la traza de tus script con printStackTrace() | aNieto2K — Mon, 01 Feb 2010 07:37:00 +0000

[...] unos días, Eric actualizó el código integrando a Google Chrome entre los navegadores soportados por la [...]