Error, no last element of zero sized array

#1 Where is it dying when you run it in the debugger (not the script debugger, a C++ debugger)? Knowing that call stack will enable Tom (or maybe me) to fix the problem; otherwise it's nearly impossible for us to track things down.

#2 When i first installed TSDev IDE and attempted to debug starter.fps I also got that error. I went through and made sure that the project settings matched the first command I put in the main.cs that is located in the same directory as the TGE executable. Here is the line:

dbgSetParameters(6060, "qwerty", true);

Don't ask me why, but port 6060 worked good for me, if you are using the default port set by TSDev which is 87?? I think, try and change it to 6060 and make sure you have the 'true' value passed in the third spot.

With the code above placed where it will be executed first in the ./example/main.cs file, and matching TSDev 'project' settings I've not seen the error since. Hope that helps somewhat.

B--

EDIT: Have you tried Torsion? Is it doing the same thing?

#3 @Bradon:

I already use the 6060 port for dubugging not working and tried Torsion before it works.

The only different thing I noticed is that Torsion always insert the following command into the first line of the main.cs script automatically:

// BEGIN TORSION
eval( "dbgSetParameters( 6060, \"6daa31a5348c\"" @ ( $dbgVersion > 0 ? ", true );" : " );" ) );
// END TORSION

I don't know if any difference here between two IDEs. I'll try run on another machine today to see if the same error occur.

@Ben:

I believe it runs without any problem in VS.net(also in Torsion IDE), so it's the problem annoying me!


Edit: typo.

#4 @Steven: After reading your post, I started putting some pressure on TSDev IDE, and also got the error you are talking about, so I don't think its your computer. I did the same things to Torsion, and had no problems.

B--

#5 I don't know if sam be able to compile a version using the old telnetdebugger?

I used to debugging using the BrainEditor Pro IDE which use the old debugger interface without any problem.

#6 I believe I've fixed the issue. It may have been from me sending invalid line numbers to the engine which may have caused that array to have issues.

You can download the update at http://torque.netmercs.net/forum/index.php/topic,12.0.html.

Thanks, Brandon, for doing some troubleshooting work and recording it. That really helped me figure out what the problem was.

Best,
Sam

#7 After applying tom's new debuger patch, the error message do not show up but the engine still crash in the debugging. Hope tom's next patch will solve this issue.

EDIT:

QUOTE from tom's reply for this error:

Quote: @Steven - I believe that the previous version could do that in some cases as the callstack was being incorrectly managed. Try the new update.

@Sam:

You may check the callstack management code inside the IDE again.


Steven

#8 @Steven - I posted this to the resource page as well. I need more details from you to get this issue solved. Is this TGE 1.4, TGE 1.3, TSE, or T2D? What is in the console log? Have you tried using a debug Torque EXE? Do you get any assert windows? When it crashes can you debug the crash in VC++? What source file and line number is it crashing in?

#9 This problem has been solved! See the quote below:

Quote from Sam's update:

Quote:This should completely fix the problem with the "Error, no last element of a zero sized array" assert failures that came up in the Torque engine.

This was caused by requests for variables (for the mouseover statistic) when the engine was not in break mode. The IDE will no longer request variable information when the engine is not in break mode.

The community rocks, thanks sam, tom, and brandon.

#10 Tom, can you please e-mail me a summary of the fix so I can file it in the bug tracker?