DAD 2/12/2014 9:14:00 AM
Debugging a crying baby as a Designated App Debugger (DAD) can be a rough job. 

When your pager goes off, it’s typically after midnight, and the crashing process has been loudly spewing a stream of inscrutable 0x80004005 HRESULTs for a minute or so. Your task is to fix the process without restarting it. WinDBG’s symbols never resolve, so you’re debugging blind. The fact that you wrote half the spec less than a year ago is of little help since the code is polymorphic and it's already evolved since you debugged it last night. 

The most trying aspect is that, no matter how heroic and valiant your efforts may be, if you can’t get the process quiescent, your boss, the Magnificent Original Maintainer (MOM), is going to swoop in make you look like a putz. 

She usually does so by merely attaching one of her specialized hardware debuggers. Either of these devices will unfailingly resolve the problem, no matter the root cause.
+ Comment
Dave '... wrote half the spec less than a year ago'. Is that what writing specs is like? I should've been a PM
Eric Hehe... It actually should have said "just over a year ago." But anyway...


< Eric's Blog Home


©1998-2020 Eric Lawrence