Hi, fellow indie dev Dan Tabar of Data Realms here, working on Cortex Command!http://datarealms.com
Been loving Decoda for years now; it's an super valuable tool for us. The debugging with our project (VS2005) works great; however we are wishing to be able to somehow make decoda show exactly where in a script that caused a crash in a lua-called piece of c++ code to occur. Basically, to make it do what this article explains:http://zeuxcg.org/2010/11/07/lua-callstack-with-c-debugger/
Specifically, to be able to pull off case #1 of the three possibilities listed in the article, so we don't have to fall back on #2 and #3!
Any tips to achieve this with decoda would be most appreciated!
Keep rocking guys, love how NS2 is turning out :]