Enhanced TelnetDebugger

#81 IHey everyone,

'm having a wierd problem using the enhanced debugger with TSE on one of my computers...

Basically, when I get all of our code from the repository and run in debug mode on one computer everything works fine. However, on a second computer, when I run in debug mode the program just hangs. It only happens when the third parameter to dbgSetParameters() is set to 'true', which I need in order to actually set break points. It looks like the torque engine is perhaps waiting for the response from the debugger, but it isn't getting it.

I though that maybe it could be my firewall or norton antivirus software, but I have the same problem when I disable those programs.

Anyone, have any ideas on what to do next to troubleshoot this?
Thanks
Todd

#82 @Eric - I'm working on it... stuff has come up that has kept me from updating it, but it's my goal for this next week to get it done.

@William - Well that third parameter would hang Torque... it just sits in a loop waiting for a connection. If one never comes then it will sit there sucking up CPU forever. I'm going to fix the CPU usage issue when it waits for the client in the next release, but i don't have a better solution for termination while it waits for the client connection.

Now back to your issue. It can also be an invalid password... if the password is wrong the connection fails and it goes back into the loop waiting for a connection. If it's not that then it has to be some network issue... firewall/gateway/etc.

Are you debugging locally on the same machine or is the debug client and the Torque game running on two different machines?

#83 Just to close out the issue I had....it turns out that an "IBM Client Manager" software that was an 'update' for my Thinkpad was interfering with the connection without giving any warning or indication. I uninstalled it and everything is working...thanks for the help.

Todd

#84 Ok the resource has been updated. I merged with 1.4 RC2 and updated all the other code branches to include some improvements from that merge. Note the install process is a little different for T2D users because i had to remove some files to make the zip smaller (sorry again).

@Steve Kilcollins - This update includes the fix for your issue. The "leaking locals" feature has been restored and your use of exec() works as expected.

This version may be a part of 1.4 final. I feel it is rock solid from my testing, but please report any issues with it as soon as possible. Thanks guys!

And don't forget to check the "Notify when new comments" below so you'll know about the next update.

#85 Tom, how does this fit with the Synapse Advanced Lighting Pack? That's a 1.3 based release right now but my first cut at integrating your mod didn't work so I thought I should check before digging into it.

#86 @Tim - I really can't say. I'm not a lighting pack owner (i know i should be), but if it's based on a modified 1.3 then you'll have to bust out a merge tool like Beyond Compare (i highly recommend this tool) and do a comparison of the files too see. I really wouldn't suspect that anything in my zip conflicts with TLK, but i really don't know.

If anyone knows or finds out please report back.

Also don't forget to delete the DSOs after you integrate the update... if you don't you'll get weird behavior.

#87 And it's in... Nice work, Tom! :)

#88 Wow...and Nice work Ben!:)

#89 Hi,

I have a problem with the Torsion debugger for Torque 1.4. I installed it like it was said in the instructions but when I debug, I receive this:

main.cs (0): Unable to find function loadDir
Illegal CodeBlock path detected (no mod directory): main.cs
exec: invalid script file name .
Illegal CodeBlock path detected (no mod directory): main.cs
exec: invalid script file name .
Illegal CodeBlock path detected (no mod directory): main.cs
exec: invalid script file name .
Illegal CodeBlock path detected (no mod directory): main.cs
exec: invalid script file name .

???

#90 @Arne - Well first of all try not integrating this enhanced telenetdebugger resource. 1.4 final should include this resource and at this time i'm not aware that you need to merge this. As soon as i get a chance i'll double check this and update the resource to note this officially.

Now the error looks very weird as it's reporting line 0 as its location. Did you delete existing DSOs?

#91 Hi everyone,

I do not know if anyone is experiencing this problem incorperating the debugger into the latest TSE head.

Basically I got this error when I start up the debug build:
core/resManager.cpp
ResourceObject::construct:NULL

I realise the extension .utf was not register in main.cpp
In main.cpp, look for

ResourceManager->registerExtension(".gf2",constructFont);

add

ResourceManager->registerExtension(".uft",constructNewFont);

#92 @Haider - Thanks for the fix. I haven't updated the resource for use with the latest TSE changes, but i will in the next week.

#93 FYI to anyone watching this thread... the resource was updated. Check the change log above.

#94 @Tom- if we are using T2D 1.1a (or TGE 1.4) do we still need to apply this resource?

alex

#95 Sorry- I just noticed the "read this first"

Quote:This resource is no longer needed for TGE 1.4 or the T2D 1.1 alpha3 release.

#96 @Alex - To further elaborate... i don't know if it is needed for T2D 1.1 alpha 1 or 2. I suspect that those were before the 1.4 final merge, so for those it is needed. Still T2D 1.1 alpha 3... it works out of the box.

#97 I've posted a patch that fixes some issues in the TelnetDebugger and exec core over here. It would be great to have as many people as possible test it before it gets into HEAD.

#98 FYI. I posted a CMDscan.l fix which was causing some breakpoints to not stick or be placed in the wrong location.

#99 I just downloaded the TGB Pro.
Can I assume that the advance TelnetDebugger is no longer needed and all I need to do is apply the telnet_fix to the latest build?

#100 @Haider - You shouldn't need to apply the current TelnetDebugger code to get started with TGB. What i'm not sure of is if my latest fixes made it in or not. Regardless i should have a new TelnetDebugger update in the next week or so that has new fixes and features. At that time i'll update this resource with the latest info on what is and isn't needed for different Torque engines.