Re: Books for advanced C++ debugging
jacob navia wrote:
[..]
That was my question. Now, please answer THAT, and if you can't
I hope you can at least keep your mouth SHUT!
There is no need to crawl into the bottle, jacob. Let's not start
telling anybody whose answers we don't like to keep their mouths shut,
shall we? This is a free forum, folks post what they see fit, and
flames don't help accomplish your goals, do they?
You're frustrated beyond your usual level, and that's not so difficult
to discern. Every once in a while we get a piece of code to maintain
and it turns out to be a hack. Annoying? You bet. Infuriating
sometimes. Sometimes after beating my head against the wall, I ask,
"why me? What did I do to deserve it?" And it often turns out that I
was given that code because people trusted me to sort it out. And that
there was nobody else close-by who could do it.
I have no particular knowledge about debugging aliasing problems to
share with you, sorry. But my approach to debugging has usually been to
replace the pieces of code that don't work (or those I don't understand)
with something I do understand and know as working. Try that. I don't
know if there is a book of recipes like that, but I don't think you have
time to study. You need to get it working.
Divide and conquer. Figure our which pieces are OK, leave them as is.
You probably already know what causes problems, see if you can replace
it keeping the same interface. Perhaps you need to introduce some
interface (to emulate the behavior of the questionable piece of code).
Ask more specific questions about C++, and you will have better answers.
But you already knew that, didn't you?
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask