[4712] WARNING!!! 'Huh, you set a test object to itself... whats up with dat?' Line 601 in function in file .\tstobj2\ObjArray.cpp

[yaz]

I'm using TestStand 4.0 and anytime I try to intialize my chasis this message shows up in my debugg viewer. I would appriciate any feedback. I have no idea what could be triggering this message or why it's worded the way it is.

[4712] WARNING!!! 'Huh, you set a test object to itself... whats up with dat?' Line 601 in function  in file .\tstobj2\ObjArray.cpp

[James_Grey]

You've hit what was intended to be an internal development warning, but apparently the warning macro used is not compiled out in the release.

This has likely been there since TestStand 1.0 and is nothing to worry about. In most cases it indicates you've called SetPropertyObject or SetPropertyObjectByOffset to set an object that was already set in the specified location. This is a harmless NOP and the warning only appears in attached debuggers, but it "might" be an indication that you have made a programming error.

I launched and exited the 4.0 sequence editor without seeing this warning, so I don't know if it is being triggered by your code module (or sequence, or custom step type, or custom UI, or custom process  model, ...) or another part of TestStand that you are using.  Chances are good that this warning does not indicate a functional problem. However, if you can reproduce it with a clean uncustomized TestStand install, I'd like to know how you did it.

I've entered a corrective action request to remove this warning.

Message Edited by James Grey on 09-13-2007 10:12 AM

[jsmalley]

I'm seeing this too and was about to post the same question. It appears anytime I step into or out of a sequence call and it's not even callling any code modules yet.

So it sounds like this one is harmless (?)

[DRock]

jsmalley,

As James stated, it seems this is simply an internal development warning.  He filed a Corrective Action Request so that this warning may be corrected for future versions of the software.  For your own reference, the CAR ID for that request is #4DC97PB8 - upon future releases, you may reference this CAR ID to see if the issue was addressed.