Hello, (first post! yay!)
So, I am trying to see if I can magically throw Decoda onto our project and have instant script-debugging goodness. So far I am having some issues.
So some info:
- We use Lua 5.1 with the LuaCoco-1.1.0 addin/mod/whatever
- We statically link Lua
- We generally have a largeish(?) amount of VMs active at a time (10-20).
- Both our Debug/Release builds produce PDBs with full debug information
So, running the debug build of our client I am able to launch and/or attach Decoda. It seems to be working properly (tracking the lifetimes of our VMs, etc). However, it reduces the client into what could be observed as 'frozen', but in reality seems to be a very dramitic slowdown the the client (tested through hooking into the client with VS.NET2005 debugger, pausing, observing that progress is being made... slowly). The slowdown is to the point of approx 1 frame per minute, so its far from usable.
So, I figured perhaps Decoda is adding a large overhead and a Release build would be more fruitful. However, when running in Release Decoda is unable to attach to the process, or launch the process. The error Decoda reports:
"Error: LuaInject.dll could not be loaded into the process"
I believe i have all Decoda project settings setup properly.. PDBs are output to the same directory in both Debug/Release builds, and in the case of release builds I did try cleansing the directory of debug PDBs (thinking perhaps decoda was looking at those?)
So, any advice would be appreciated. Decoda looks like it would be a pretty cool tool once I figure out how to work with it.
- Is Decoda not compatible with LuaCoco? This might explain a lot.
- Is Decoda poor at handling large amounts of VMs? How about fairly rapid creation/destruction of VMs?