Yes, I know the purpose of the dots. I guess my origninal post didn't
explain what I had tried well enough.
I can cut out a block of code and source debugging works, pasting it
back in breaks source level debugging. I was guessing that I've
reached some sort of limit to the number of symbolics output. That is
why I thought turning off some debugging dots might fix the problem.
It has not.
-doug
>Yes, I know the purpose of the dots. I guess my origninal post didn't
>explain what I had tried well enough.
[quoted text clipped - 4 lines]
>why I thought turning off some debugging dots might fix the problem.
>It has not.
I think the limit of symbolics was fixed a few years ago. You shouldn't
have to turn off the files but it was worth experiementing.
Is this a straight library or a DLL you are debugging. there are
problems with dlls and frameworks, they have gotten better over the
years but there are still problems. If this is strictly your program
code then you might have a bad debugger cache or something where the
debugger is chasing the wrong file.
Ron

Signature
CodeWarrior Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and our staff
-- http://www.codewarrior.com/community --
Ron Liechty - ron.liechty@freescale.com - http://www.codewarrior.com
norton.doug@gmail.com - 08 Dec 2005 15:33 GMT
Man, I've tried everything. Cleaning the project, deleting the data
folder, removing all CW cache and prefs, turning off just about every
"dot" (I have around 480 files in my project) and still nothing. The
only thing that seems to make it work is commenting out the 15 or 20
lines that seem to have put it over the edge. Comment out those lines
and source level debugging works.
The funny thing is my project has 2 targets, a Mach-O and CFM. CFM
always works, it's Mach-O that I see the debugging problem.
-doug