Telenet Debugger / Torsion Bug

The capitalization you use when you execute your script files must match the actual file/folder capitalization, or, if it does not breakpoints specified in those files will not be hit. Although the script files will still execute and you can still step into the code if it is from an outside breakpoint, "breakpoints in a script file that is executed with capitalization not matching the actual file capitalication will not be hit."

I believe this is a new bug introduced in 1.5.1 in the telenetdebugger code.

For example, if you execute like this:
exec("./gamescripts/scriptfile.cs");
But the actual folder is "gameScripts"...

The fix involves making two changes to telenetdebugger.cc

Replace this function (this is the new version):
(Actually just the string comparison is changed)

TelnetDebugger::Breakpoint **TelnetDebugger::findBreakpoint(StringTableEntry fileName, S32 lineNumber)
{
   Breakpoint **walk = &mBreakpoints;
   Breakpoint *cur;
   while((cur = *walk) != NULL)
   {
      // TODO: This assumes that the OS file names are case 
      // insensitive... Torque needs a dFilenameCmp() function.
      if( dStricmp( cur->fileName, fileName ) == 0 && cur->lineNumber == U32(lineNumber))
         return walk;
      walk = &cur->next;
   }
   return NULL;
}

In this function,
void TelnetDebugger::addAllBreakpoints(CodeBlock *code)
Change the beginning of the while look to look like this:
(Just the string comparison has changed)

while((cur = *walk) != NULL)
   {
      // TODO: This assumes that the OS file names are case 
      // insensitive... Torque needs a dFilenameCmp() function.
      if( dStricmp( cur->fileName, code->name ) == 0 )
	   {

Note: all we are doing is replacing the existing method of comparing two string table entries with a case insensitive method (dStricmp).

Edit: Or now that you are aware of the issue, just watch your capitalization when you "exec".