| ??? 09/24/06 09:51 Read: times |
#124939 - debuging C code |
Following an incident with one of my colleges I thought I should pass on this tip about debuging compiled C code in either a simulator,emulator or 'by hand' as it were.Remember that it is very often the case that C code which has been optimised at compile time is impossible or at least very difficult to debug, the compiler will perform various optimisation routines which mean that stopping a simulator at a break point and changing a variable can cause unexpected results and very strange behaviour.I always keep a debug version of the compiled source where all the optimizations have been turned off and the code can then be run in a simulator and the code will behave as expected.
|
| 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 |