Yesterday, I found a couple of useful debugging tools within VS 2005, the Immediate Window and Tracepoints.

Immediate Window

Have you ever gotten an assert in your own code from an invalid operation in a Win32 API?  How do you know what the failure inside the API was?  You put in a GetLastError(), right?  What if the function is called from a library that you either can't change or don't want to recompile?  Answer: the Immediate Window (Ctrl-Alt-I).

I was recently debugging a threaded application that was failing inside of CreateThread().  Instead of rebuilding the library calling the API, I simply brought up the Immediate Window and typed in:

It immediately responded with the error, 1450.

You can call your own methods, print out variables and even create new objects.  Read the documentation for all the details, but this is a nice way to get yourself quick answers about your code.

Tracepoints

A tracepoint is a great way to quickly generate trace messages without inserting code.  This is intended for temporary debugging only as they aren't included in any shared source.

I've found this very useful in tracing multithreaded code.  It can be a pain in the rear to get print messages that is sync'd up with the execution of a line.  I haven't been able to confirm this yet, but I believe tracepoints execute and print in an automic manner.  This obviously makes it slow, but I'm suspecting that it's output would be the same as locking around execution and print without the side effect of altering the synchronization of your non-traced code.

Creating tracepoints is a two step process.  You first set a breakpoint on a line, then you convert the breakpoint to a tracepoint by adding the condition, "When hit...".  If using Visual Assist, you must convert via the Breakpoints window directly, a right click on the breakpoint will not suffice.

These were written from the context of game development, but they are still very applicable outside the industry.

• Simple is Beautiful, reminds me of class design sections from Code Complete.
• The Care and Feeding of Pre-Compiled Headers
• Physical Structure and C++ Part 1
• Physical Structure and C++ Part 2

Paradigm just gave us our own retail copy!  Choice of 360 or PS2...looks like I'll be playing it tonight!  Sweet!

Be prepared for the barrage of marketing that will be thrown your way this weekend and next week surrounding the Tuesday 8/28 launch.  I've been told that some Gamespots have already began selling their copies...tsk, tsk. 

We're going to be featured on the octagon in tomorrow's UFC championship fight and one of the fighters will be shown playing our game.  FOX, ESPN, USA, Discovery, Comedy Central and a load of other channels will be featuring our 30 second spot for a total of over 500 unique showings. 

It's out tomorrow!

Apparently, the trailer isn't being shown in all the theaters that the Bourne Ultimatum is being shown.  It appears they're going for larger markets and bigger college towns.  I'm not sure how long the trailer will be shown, but I'll be checking it out very soon. Here are some theaters showing the trailer in our old stomping grounds from WA and AR.  Sorry Jonesboro, no trailer for you.  You'll have to come to TX for it.

• Tandy Movies 10, 4188 E. McCain, Little Rock, AR
• Lakewood Cinema 8, 2939 Lakewood Village Dr., Little Rock, AR
• Breckenridge Village, 1200 Breckenridge Dr., Little Rock, AR
• Capital Mall, 625 Black Lake Blvd. SW, Olympia, WA
• Gig Harbor 3, 5401 Olympic Drive NW, Gig Harbor, WA
• Tall Firs 10, 20751 State Route 410 E, Bonney Lake, WA
• Longston Place 14, 13317 Meridan St E, Puyallup, WA
• Martin Village Stadium 16, 5400 E Martin Way, Lacey, WA
• South Hill Cinema 6, 3500 S Meridian, Puyallup, WA
• Lakewood Cinema 15, 2410 84th St S, Lakewood, WA