Space geek at work

If anyone ever tries to tell you that NASA isn’t worth the tax dollars we spend on it, you just look that person straight in the eye and say, “Oh YEAH??  Well, did you know that NASA has a program you can use to view accumulated imagery and data on our planet?”

This thing isn’t the marvel of programming that Google Earth is — it’s slow and occasionally tripped up by graphical errors, at least on my system — but I’m pretty sure there’s at least as much, if different, information available.  Standard satellite pics are augmented by LandSat data, up-to-date imagery of natural phenomena, wider availability of high-res data (I can see my house!)…  Data on agriculture and climate indicators, Galileo imagery, weather maps, animated satellite views of the aurora borealis and other stuff of interest.

That this alone is easily worth $16.3B annually in our federal budget of seventy hundred hojillion kabillion dollars should be more self-evident than salsa on tortilla chips.  It even comes with a built-in wigital diga-whatchamaha.

NB:  The current version is .Net and DirectX dependent, so it’s twitchy on WinXP and Vista, and doesn’t run at all on other operating systems, but the next version, est. beta April 07, is scheduled to be Java/OpenGL.

Plugging the leaks

While trying to track down an annoying memory leak with Visual C++’s debugger, I ran into an issue under which the _CRTDBG_MAP_ALLOC preprocessor flag will make it appear as though the leaky allocations all take place in crtdbg.h (where overloaded, locale-recording versions of the new operator reside).

The fix outlined in this article almost worked (using allocation breakpoints didn’t work at all), but my compiler had a hissy fit about the redefinition of the “new” operator in the supplied function. Perhaps I could have tracked that down, but my inherent laziness prompted me to a different route — collapsing the function and the #define into one. This worked fine and got me the actual location, in my program code, of the offending chunk of dynamic memory:

#ifdef _DEBUG
#define new new(1, __FILE__,__LINE__)
#endif

Don’t know whether my problems with the previous fixes stemmed from compiler settings, project differences, or versioning differences, but the above may be handy for anyone else who needs to track down a leak in VC++ 2005 Express.

Do I need to learn maniacal laughter?

Dude.  I want the statue that goes with the Casey and Andy mad science award.

I tried to learn maniacal laughter for kung fu once (no, seriously) and I was no good at it.