Unfortunately the version that I found to "do...

2010-05-09T13:05:49.423+07:00

Unfortunately the version that I found to "do it" is just to place the "try-catch" clauses to EVERY method and then assemble the stack trace from Globally Unique ID-s (GUID-s). Then, I also wrote 2 scripts for the KomodoIDE:

One is "UpGUID", which replaces GUIDs within the selected text region in the KomodoIDE. I write code in NetBeans, because it has a better Vim emulation than the KomodoIDE and the NetBeans has really fine code template system, so I don't have to write all the try-catch-with-a-constant-GUID by myself. However, the KomodoIDE has an easier way to integrate my own weird tools, so I use the 2 in parallel.

The other tool that I wrote as a KomodoIDE "toolbox item", reads in the custom-generated stackt-trace and allows me to move up and down within that stack trace in a way that with every movement, the code region, from where the exception has been thrown, is opened and displayed in the KomodoIDE code editor. As the GUID-s are unique, it's possible to grep the place out and displaying the text region in the IDE was just a matter of scripting.

I found out that that sort of stack-trace navigation by instantly displaying the code region, from where the exception got thrown, really boosted my productivity.

I haven't uploaded the script collections to anywhere, because they're a bit of a mess, but they work and if You want, then I can send them to You. They're a mixture of Ruby, Bash and JavaScript. The KomodoIDE is manipulated by using JavaScript.

I also wrote a little about it in my blog: http://mv-veebilog.blogspot.com/2009/08/about-javascript-line-and-this.html

Comments on YourSway: 3 painful ways to obtain a stack trace in JavaScri...

Unfortunately the version that I found to "do...