Slashdot Mirror
Pet Bugs II - Debugger War Stories
AlphaHelix queries: "A few weeks back there was an article on Pet Bugs, where people were asked about their favorite bugs. I have a different sort of question: what was your greatest debugging challenge? I've been debugging for a long time, from analog circuits all the way up to multi-kLOC multithreaded servers, and I have some pretty grisly war stories, like the time I debugged a problem in a third-party DLL in machine code because the client didn't have the source for it (yay open source.) What was your greatest debugging triumph?" The first time Slashdot did this it was more about bugs that you had encountered (and may not have solved), this one is about bugs in your own projects code and the trials and tribulations you had to go thru to get them fixed.
Pussy. MFC debugging is easy. All the source is there on the Visual Studio CDs and the VS Debugger is great. Hell, it's one of the EASIEST things to debug. MFC's problems lie within its architecture, not within the execution of said architecture.
What'dya mean there's no BLINK tag!?
Um, Microsoft rules eh; if that's not ms-troll I don't know what is...
However you are missing the point; setting aside it should have been implemented as assert and not Assert, it was the none standard behaviour in what was supposed to be an ANSI compliant C++ that is the real issue. So yes, that behaviour is none standard, and since practically every C++ programmer I know, who used VC++ including some world class acts and apparently plenty of slashdotters, fell for it. It is the Microsoft convention that was/is wrong, it is counter intuitive, so yes it was/is YAMB (Yet Another Microsoft Bug). The MASM segmentation alignment issue is the another example of the same attitude.
We are always right and that is the way it works,
that is the way it works, so you are wrong,
if you are wrong, we are right;
we are always right. ad nausium..
So that is why when Microsoft break a convention or standard and the fault is everybody elses.
Well frankly you need to grow up and down scale your ego, think freely instead engaging in group think and start listerning to others. Don't you know the customer is always right. So if we raise something, you should appologise for wasting my time, thank me for the contribution, and don't under any circumstance imply I'm stupid simply because my opinion differs. That really pisses me off about Microsoft consultants ops I mean 'evangelists'. I wonder what prat though it a good idea to send out 'evangelists' to preach 'belief' to 'Engineers'?
The best laugh I ever got at an evangelists expense was telling him that nature provided him one mouth and two ears and perhaps he should use them in that ratio and then he may understand our requirements. Did he shut up ? Well for about 3 seconds, before launching into his spiel.
So yes, none standard behaviour is YAMB (Yet Another Microsoft Bug), it is not RTFM.