Game Development Community

Debug_guard

by Sebastien Bourgon · in Torque Game Engine · 08/30/2005 (7:22 am) · 6 replies

Has anyone gotten DEBUG_GUARD to work in 1.3? (I tried HEAD which I'm told it works in but none of the problem files have changes so really dont know where to look to fix it in 1.3)

About the author

Former Indie Game Developer for Max Gaming Technologies. I then spent a couple years doing mobile work for Capcom Interactive Canada, the highlight being Mega Man II for iPhone. Now doing various mobile contract jobs (mostly iPhone)


#1
08/30/2005 (9:29 am)
Worked in 1.3, works in 1.4... Where are you running into problems?
#2
08/30/2005 (9:38 am)
PathManager.cc
d:\MaxGaming\loreengine\engine\sim\pathManager.cc(50) : error C2065: 'mPaths' : undeclared identifier
d:\MaxGaming\loreengine\engine\sim\pathManager.cc(50) : error C2228: left of '.setFileAssociation' must have class/struct/union type
type is ''unknown-type''
interiorRes.cc
d:\MaxGaming\loreengine\engine\interior\interiorRes.cc(23) : error C2065: 'mPaths' : undeclared identifier
d:\MaxGaming\loreengine\engine\interior\interiorRes.cc(23) : error C2228: left of '.setFileAssociation' must have class/struct/union type
type is ''unknown-type''
#3
08/30/2005 (11:05 am)
Greetings!

Sebastien, that looks like DEBUG_GUARD is actually doing its job. If you look in both those files you'll see a VECTOR_SET_ASSOCIATION(mPaths); but there is no mPaths member defined for either of those classes. Comment out those two lines and you'll be good to go.

This was a problem with stock TGE, and I don't know if it has been recently corrected. As Ben isn't seeing an issue with DEBUG_GUARD, I suspect that it has. :o)

- LightWave Dave
#4
08/30/2005 (11:08 am)
Those lines aren't ifdef'd out in head or 1.3 so I dont see why my fix should involve doing that.
#5
08/30/2005 (11:23 am)
Greetings!

Fair enough. All I can say is that it worked for me and I'm happily using DEBUG_GUARD as we speak.

If you come up with a different fix that doesn't involve commenting out code that isn't being used, please do share! :o)

- LightWave Dave
#6
08/30/2005 (11:39 am)
It's entirely likely that I just removed the lines and never checked the fix in. I _am_ running debug guard regularly in 1.4RC2 development, so I don't anticipate that 1.4 will have the problem. Meanwhile, go ahead and get rid of them. The VECTOR_SET_ASSOCIATION macro exists to make it easier to figure out where Vector<>'s came from; having it for non-existent members won't get you far.