Possibly nasty bug in TSShapeConstructor::addSequence() - LOGGED

I don't know why this doesn't cause problems more often, since I just caught it by chance. In the TSShapeConstructor addSequence console method body, there's this:

if (object->mShape->addSequence(fileBuf, seqName, destName, startFrame, endFrame, &totalFrames))
{
   ADD_TO_CHANGE_SET();

ADD_TO_CHANGE_SET() is a macro that defines this:

object->addToChangeSet(argv[0], argc-2, argv+2);

My game was suddenly fatally asserting after adding some animations due to argv[0] being NULL and being passed to dStrcmp() somewhere inside addToChangeSet(), which doesn't make sense, since argv[0] is the method's name and isn't supposed to be NULL nor change like this. A data breakpoint revelaed that it was modified in StringStack::getArgcArgv() *during* the executing of mShape->addSequence(). To be specific, it happens when the resource manager uses eval() to call exec() on the shape's .CS file automatically.

It became obvious that the argv array is shared and calling console functions/methods within the body of another console function/method can override it, making them not safe to be read afterwards.