tracegl for JavaScript debugging

In preparing for my new Node workshop (tickets go on sale Wednesday 10am – set alarm!) my tool of choice used to be node-inspector but development has gone idle (for a year to date) and it’s showing it’s age. However, recently I came across tracegl I was intrigued as it looked to add to my debugging tools for Node.

tracegl was so much more than I realised: it captures full JavaScript state a all points of my application’s execution – both on the server side, but also the client side.

Debugging a real bug with tracegl

Rik Arends includes an introductory video on the site, and the script is €12 – which frankly is a steal for what it provides me. If you’re join my Node workshop – I’m proving a licensed copy for everyone (because I think it should be part of your core stack).

I’ve included a short video of how I’ve used tracegl to debug my server side application. A few important things to note are: the trace is historical – and not blocking execution, which is what I’d normally do if I had to debug: I’d carefully replicate the issue, then either add a conditional breakpoint or debugger statement – but with tracegl, the bug can occur, and if tracegl is running, I can just look back at the state of the problem.

Learning more

I’m running a new crash course in Node on July, and similar the past it’s known to have sold out in a week. Tickets go on sale on Wednesday at 10am (UK) and will be available here.

I’ll be using this tool and many others to give you a fully packed day of knowledge on how to use Node, how to develop sites and real-time applications, and what tools I use for debugging, publishing and deployment.

So grab a ticket if you want my hands on, “knowledge smash & grab” course (or check out more details here).

One Response to “tracegl for JavaScript debugging”

  1. What a coincidence – I bought tracegl a few weeks back. I just havn’t used it much (mostly because I havn’t had the need to). However, I feel it’s missing a few niceties that would make it the most complete debugging tool. For example, being able to set breakpoints that stop code execution (with step in/step out). Take that one step further, I’d also love to be able to edit the code live and have node.js update, similar to how node-inspector works. I couldn’t get node-inspector to work though. Which is a shame. I was looking forward to live code editing. =(

Leave a Reply
Not required

CODE: Please escape code and wrap in <pre><code>, doing so will automatically syntax highlight