Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pjcast]

Well, for Ogre Studio, I have started adding a remote script debugger. And so far, it works well. Except, it doesn't yet support break points or watches, or examining runtime variables (although, you can get debug output of their contents).. but nothing pretty with that part.

Stay tuned...

[pjcast]

Ok, I've modified WGE to accept remote debugger connectios. Currently, it is always waiting at start up for a connection. What I plan to do, is make it a cmd line flag. Plus, I want to make it a runtime settable thing too.. So, that from the running game, it can be attached anytime.

Anyways, i had to make a couple changes: when compiling the script buffer, the filename is now correctly used to uniquely identify the src of the script being ran, and debugging information is embedded in the script when the debugging flag is turned on. Which means, if this were to be used at runtime, in order to break execution, the script has to have debugging info turned on (I'm not sure, it may have a speed impact).. So, this may need to be turned on the whole program - perhaps only in the debug build of WGE by default.

[pjcast]

Break points adding / removing works. There is a sligt hickup in the net reading code, which can create invalid xml - which will be fixed shortly - as it causes invalid state data.

Besides that, next will be variable listings

[mysterycoder]

Are you planning on leaving the code to listen for remote debugger inside the Game project? If not, where would you stick it in WGE?

I'm thinking about how this could fit in with the abstraction of scripts.

[pjcast]

There could be a virtual method like: enableDebugging(bool enable); in te script manager to allow this