??? 09/26/06 04:18 Read: times |
#125045 - Pointers Responding to: ???'s previous message |
Differences in behavior (other than timing) between debug code and non-debug code are almost always due to pointer problems. Have all pointers been properly initialized? Are array bounds being violated? Can two routines update a pointer so that one is using a no longer valid pointer?
Note that if you have pointer problems, they still exist in the debug code, although they may not manifest themselves, at least not frequently. Any manager who would ship debug code on the basis that "it works ok", when the optimized code doesn't, should have the letters I, D, I, O, T carved into his forehead. Then he should be fired. |
Topic | Author | Date |
debuging C code | 01/01/70 00:00 | |
Management solution | 01/01/70 00:00 | |
I kind of hope | 01/01/70 00:00 | |
False assumption | 01/01/70 00:00 | |
to HLL or not to HLL | 01/01/70 00:00 | |
Things for which an HLL cannot be trusted... | 01/01/70 00:00 | |
sometimes there's no other way | 01/01/70 00:00 | |
that was not me, but Andy | 01/01/70 00:00 | |
Timing - end of wrong stick | 01/01/70 00:00 | |
Thats not the point | 01/01/70 00:00 | |
better, don't use C at all.. :-) | 01/01/70 00:00 | |
experience and knowledge | 01/01/70 00:00 | |
the key word is "manifest" | 01/01/70 00:00 | |
NASA | 01/01/70 00:00 | |
against NASA rules, sorry Andy posted before | 01/01/70 00:00 | |
Testing | 01/01/70 00:00 | |
Pointers | 01/01/70 00:00 | |
In the real world | 01/01/70 00:00 | |
worse than that | 01/01/70 00:00 | |
customers complaining or not ... | 01/01/70 00:00 |