This is a generic unhandled exception error msg that could be a bug in QALoad, but most likely has to do with script modifications. I've most often seen this error for script mods involving strings and the error related to memory management.
What version are you using? What middleware? What script modifications did you make.
To give you an istance of this error, I created it one time by passing a string in printf() call for a %d parameter. It didn't show up with 1 VU but did for more than 1 (as it was overwriting some memory) and I got error msg.
I'd recommend staying away from the char pointers and null terminated strings of the old c-style script functions.
Instead of the EZ Script function DO_ExtractString, use the Visual Script ExtractString function.
Also be sure to use the CLoadString type (class object) for your strings instead of char pointers with the Visual Scripting functions, you then do not need perform the free command. The CLoadString class gets rid of most of the memory problems.
I'd bet these will clear up your issue... let us know.
I have the same problems the strcat and strcpy functions create problem when char pointer, simple char and CLoadString are used.
The only way to debug is checking line by line for that use EXIT(); function
say copy EXIT(); @line 99
then validate if gracefully exit then put that EXIT() function after next immediate command say line 101, if some command is at line 100.
Do it @workbench only.
I know its a hard way but i believe its the only way.
remember to free char pointers at convenient place.
I solved this in the similar fashion by cleaning up the char pointers, but this kind of vague message is poor in QAload..
[/ QUOTE ]
I disagree with this statement. The message is true. The VM crashed. You are asking for the tool to determine what caused the crash. However, with the unlimited possibilities of what you can write in your script the cause could be anything. I think you will determine the cause of these messages quicker with more experience with the tool.