Can't debug anymore...

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Kurt - 25 Jun 2005 17:28 GMT

When I start a debugging session, rather than starting at main() in
source, I start in assembly. Choosing "Run" results in the warning:

The process is already starting

If I choose Step Out a few times I get past a couple assertion failures
and the program runs. It seems to run fine, but no breakpoints ever get
hit.

I can recall this "process is already starting" error occurring before,
but only sporadically, and killing it and trying again always worked.
Now, it happens every time.

Any advice how to get debugging working again?

Kurt

Reply to this Message

MW Ron - 27 Jun 2005 21:05 GMT

>When I start a debugging session, rather than starting at main() in
>source, I start in assembly. Choosing "Run" results in the warning:
[quoted text clipped - 4 lines]
>and the program runs. It seems to run fine, but no breakpoints ever get
>hit.

What are your settings in the target and global debugger settings. It
could be that do not have the start at main set. However since you say
breakpoints don't get hit I'd think it is more likely a corrupted cache.

In the global settings purge the debugger Cache. Make sure you have
don't step into runtime selected. Remove all sym files for your
project. See if it works then

If not see if this happens on just one project or more than one.

more information on system and version of Codewarrior etc.
Ron

>I can recall this "process is already starting" error occurring before,
>but only sporadically, and killing it and trying again always worked.
[quoted text clipped - 3 lines]
>
>Kurt

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 - MWRon@metrowerks.com - http://www.codewarrior.com

Reply to this Message

Kurt - 28 Jun 2005 02:40 GMT

> What are your settings in the target and global debugger settings. It
> could be that do not have the start at main set. However since you say
> breakpoints don't get hit I'd think it is more likely a corrupted cache.

Thanks Ron, but this was my problem, not CW's.

I ended up fixing it by re-building everything. I have a separate
project to generate pre-compiled headers, which are used in several
other library projects, and my main application project. I had let the
pre-compiled headers get out of sync with changes I had made in my
application base class, thereby confusing the debugger.

Kurt

Reply to this Message

Mac Forum / Programming / CodeWarrior / June 2005

Can't debug anymore...