??? 06/21/07 14:26 Read: times |
#141132 - Optimization Level ? Responding to: ???'s previous message |
Recently there have been discussions that talk about high levels of optimization causing debugging problems. It's when more than one subroutine share some common code (optimized) and the debugger can't determine which routine is using this shared code. Anyway that's the way I understand it.
You might try no optimization and see if that makes the problem go away. I don't C, so I'm not an expert. Just my two cents. You might look at this thread to see what I'm talking about. http://www.8052.com/forum/read.phtml?id=140088 Jon |
Topic | Author | Date |
stepping throught "c" code | 01/01/70 00:00 | |
Optimizations. | 01/01/70 00:00 | |
Optimization Level ? | 01/01/70 00:00 | |
Yep, very likely the optimization | 01/01/70 00:00 | |
Fly what you debug; Debug what you fly | 01/01/70 00:00 | |
Fly what you TEST; TEST what you fly | 01/01/70 00:00 | |
It's about time | 01/01/70 00:00 | |
OH? | 01/01/70 00:00 | |
Re: OH? | 01/01/70 00:00 | |
If you have a very complicated calculation | 01/01/70 00:00 | |
break it up | 01/01/70 00:00 | |
I give up | 01/01/70 00:00 | |
Nevermind![]() | 01/01/70 00:00 | |
Debugging problems | 01/01/70 00:00 | |
Update | 01/01/70 00:00 |