Bryan will appreciate this; I was at work yesterday from 9:30 to 20:30 coding to fix some failing tests that came about from a code merge that exposed bugs in my code and a lack of docs in something I was using. Some real nasty stuff that involved C++ debugging in a situation where getting gdb to go was not really an option.
Trick learned for the day? In C++, when printing debugging output, make sure to flush the output. Supposedly ending an iostream with endl will do it, but I don't know if that is guaranteed by the Standard Library spec so I would always end a stream with flush; ``cerr << "bad things happen when docs don't tell the whole story" << endl << flush;``.
1 comment:
It was pretty crazy last week, they found a bug in our product and Beta was 4 days away, so some of the developers were here from 8am in the morning Wed, until 6 am Thursday morning. After that, they went home, but the solution causes some other problems, so they called them back, and all of them working from 11am Thursday until 4 am Friday. he he he, I love crunch time :)
Post a Comment