Error, Failed to resume target process., Bad arguments passed to function

[VinceTF]

Got into work this morning, opened a known good project, started the debugger as I normally do and got the following error message, "Failed to resume target process., Bad arguments passed to function"

Note that the P&E device is connected and both LED's are on.

What could be causing this issue?

-Vince

[Monica]

Hello Vincent!

How is the project going?

We'd like to know! :smileywink:

Regards!

[VinceTF]

It's working well now.  Thanks for checking in.

[Monica]

Great!!!

We'll be around!

[BlackNight]

Hello,

could you check your launch/debug configuration? It could be that no target/debug connection is set up?

Erich

[VinceTF]

Erich,

Thank you for your quick response.

I checked the debug configuration and it is unchanged from when the project was working.

It looks like I was able to resolve this issue by doing the following:

1) Exit codewarrior Eclipse.

2) Navigate to: Workspace directory\.metadata\.plugins\org.eclipse.core.resources\.history

3) Delete all folders except for 0 and 1 in this directory.

4) Restart CW and debug.  Now the issue is no longer observed.

[BlackNight · Accepted solution]

Hi Vincent,

hmm, I do not believe that .history folder had an impact. This .history folder is for the Editor only as far as I can tell (see CodeWarrior Tool Tip #3: History repeats itself).

But what I think is maybe more that you had a DE.exe zombie running (the debugger engine did not respond any more). With shutting down eclipse that problem was 'solved' for you. If this happens again to you, see Killing Me Softly: Zombies and Debugger Engines | MCU on Eclipse

Regards,

Erich

[VinceTF]

Thanks for the info.  I'll be sure to keep an eye on DE.exe in the future.

BTW, I performed several restarts of CW which did not resolve the issue.  This is why I thought clearing .history may have solved it.  I guess I just got lucky on the last re-start.

[BlackNight]

Usually closing Eclipse closes as well de.exe. But in case this fails, it is still there and causes problems. Up to the fact that there might be multiple instances running (and this causes problems). A reboot of the machine definitely 'solves' that situation. Killing the de.exe from the task manager is much faster and does the same thing.