Debugging

#1 The easiest way to do this right now is....

1. Launch Torque with the VS debugger.
2. In the Torque console use dbgSetParameters() to init the TelnetDebugger.
3. From Torsion use 'Debug->Connect' to connect to your game which is already running.

I'll think i've got an idea on how to make this process much easier... i'll add it into my Torsion todo list. =)

#2 Great, I'll try it when I get home thanks!

#3 Ok. I got it to run the game from vs.net and was able to connect to it from torsion. it allowed me to step through the torquescript through torsion but as soon as it was supposed to go to vs.net it didn't stop at any of the many breakpoints i had set. Any clues?

#4 Torsion/Codeweaver are script (only) debuggers. They don't tie into your source code. To do that, you need to use a c++ debugger IDE.

#5 Yes, I'm using vs.net 2005. I hit 'run' on vs.net 2005 and then 'connect' to it from torsion for the torquescript side of the debugging. however, the breakpoints in vs.net 2005 that i have set aren't stopping the code execution at any point.

#6 @Jonathon - You sure your running a debug build? It has to be some simple mistake like that.

#7 I do have it in debug mode. However when I mouseover the breakpoint in vs.net it says:

"The breakpoint will not currently be hit. No symbols have been loaded for this document"

I think I've been doin too much C#.net ;)

#8 Try doing a full rebuild of the code. Also make sure it is running the debug exe. I've had this happen to me before and a combination of VC++ restarts, rebuilds, and stuff finally fixed it.

#9 This is 1.4, and it's called TorqueDemo.exe now I believe right? I did a search and none of the .exe's have 'debug' in them??

#10 Well, I've completely started over a few times and every time I run the program, even in debug mode, the breakpoints in vs.net 2005 hollow and when I mouse-over them they say:

"The breakpoint will not currently be hit. No symbols have been loaded for this document"

Any ideas?

#11 I just built a debug version of the engine straight from the distro directory and was able to see breakpoints just fine... it broke for me in a COnsoleMEthod of guiCanvas in fact.

So, it sounds like you're still using a release build. I think that's the default configuration. Did you set your Active Configuration to Debug ( under Build>Configration Manager in VS)? When you build, the first line of the output tells you what it's using...

#12 Jonathon -
it does indeed sound like you're running a Release build in Debug mode.
To compile a debug build, select Torque Engine as your current project,
then go up to Build | Configuration Manager, and under "Active Solution Configuration" choose 'debug'.

at least, that's where it's hidden for me in VS 2003.

it may need to recompile the whole SDK, so it could take a while.

#13 Yes, I selected debug under configuration manager for all the projects, not just the Torque Demo project. I'll paste in the output window to verify once I get home. When I set the breakpoint, it looks as if it's going to work until I actually run it, that's when I get the "breakpoint will not be hit" problem stated above.

#14 Hmm,
are you sure the "active solution config" is debug ?

If you don't have a "TorqueDemo_Debug.exe" right next to "TorqueDemo.exe", it's not making the debug build.