Ben Combee <[EMAIL PROTECTED]> wrote in news:99400@;palm-dev-forum:
> > At 16:44 2002-10-27 -0800, you wrote: >>This would be #4. The code in question was definitely being executed, >>and from what I could tell, was working correctly as programmed. I use >>CW about every day, and ver 8 since it came out, and have only seen >>this problem that one time. Seems less than not very often to me. > > It is still too often for me to be happy about it. > > I've not had a chance to dig into the linker code or the debugger code > that handles symbolics files... however, you can do some diagnosis > yourself using the "disassemble" command. There's an option to > include debug info in the disassembly, and you can use that to try to > verify that debug info for your function is correct. That only tells > you the compiler did the right job, however -- its still up to the > linker to pull all the debug info correctly and fix it up for the > output pSYM file, and to the debugger to read this file correctly and > associate it with all the code segments. As you can imagine, this can > be a bit complex, and when a problem is intermittent or only affects > large cases, its hard for us to track it down in our normal testing. > Thinking back to this, I seem to remember it happening after many debugging sessions from that one CW startup. I don't seem to remember it happening later. So it might be something gets slightly corrupted in the debugger after being run awhile. This hasn't happened since then, but if it shows up again, I'll do the above. Todd. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
