topic Automated Debugging - Workspace seems to be different than the one given. in Classic/Legacy CodeWarrior

Automated Debugging - Workspace seems to be different than the one given.

kt3072 — Tue, 08 Feb 2011 21:03:13 GMT

Hi,

Im trying to run a TCL script in the debugger using CW 10.1.8. The script starts but the Multicore Launch configuration cannot be found. There is also no Project visible in the CW Projects window.

I start eclipse in the following way:

cwide.exe -data D:\Documents and Settings\foo\workspace-1.8 -vmargsplus -Dcw.script="{D:\Documents and Settings\foo\workspace-1.8\AutoBuild\runTest.tcl}"

The TCL script looks as follows:

pwd
debug -name ADS_XYZ_2Cores
mc::group removeall
mc::group new MSC8156
mc::group enable 0.0
mc::group enable 0.1
mc::go

The output in the IDE Debugger Window looks as follows:

----------------------------------------------------------------

CodeWarrior Debugger Shell v1.0
%>source {D:\Documents and Settings\foo\workspace-1.8\AutoBuild\runTest.tcl}
pwd
D:/Documents and Settings/foo/workspace-1.8/AutoBuild
cmdwin::eclipse::debug -name ADS_XYZ_2Cores

Error: no launch configurations exist

----------------------------------------------------------------

After starting the IDE the CodeWarrior Projects Window is empty. Normally I would expect the project to be debugged to exist in there. I can import the project into the Workspace and then the script does get further but the project starts with the wrong Build Configuration and so a Build is triggered interferring with the debugging.

I'm wondering now whether the workspace/configuration is different in some ways for the IDE when called from the command line.

Also, if there would be a way to set the Build Configuration I would be glad.

Regards,

Killian

Re: Automated Debugging - Workspace seems to be different than the one given.

J2MEJediMaster — Tue, 08 Feb 2011 23:17:16 GMT

Here are several suggestions:

1) I do not know why you are enclosing your directory path with curly braces. The double quotes alone should do the job. They do not seem to hurting anything, but still...

2) Add the argument -data to specify the project's workspace. Here's an example:

"C:\Program Files\Freescale\CW SC v10.1\eclipse\cwide.exe"
-data D:\workspace_StarCore
–vmargsplus
-Dcw.script=D:\workspace_StarCore\FIR_filter\tcl_test.tcl

Since your project is outside of the workspace, you probably need to modify the data arument. I would strongly recommend that, until you get this working, you run the project from within the workspace directory.

3) If your launch configuration is named ADS_XYZ_2Cores, try the following for the debug command:

debug {ADS_XYZ_2Cores}

---Tom

Re: Automated Debugging - Workspace seems to be different than the one given.

kt3072 — Tue, 08 Feb 2011 23:46:51 GMT

Thanks for your reply.

To provides some answers:

1) If I omit the curly braces I get

CodeWarrior Debugger Shell v1.0
%>source D:\Documents and Settings\ktimmler\workspace-1.8\AutoBuild\runTest.tcl
Error: wrong # args: should be "source fileName"

Since I'm using Perl the quotes probably get evaluated at some stage, I guess I could try harder, but it seems to work ok.

2) "-data" is in there right at the start:

cwide.exe -data D:\Documents and Settings\foo\workspace-1.8 -vmargsplus -Dcw.script="{D:\Documents and Settings\foo\workspace-1.8\AutoBuild\runTest.tcl}"

3) I will give it a try. I have to add that importing the project into the empty workspace lets the debugger run, so I assume that the command is right, just the environment isn't.

The problem is that the source code will always reside outside the workspace since it is in a Clearcase view. I can put the scripts near the project files but to get the source/project into the workspace I would have to mount the view in the workspace which would require some UNIX like features under Windows XP which I'm using. Maybe I can mount the view under a directory under windows now though.

I'll have a closer look at things, thanks for your help.

Regards,

Killian

Re: Automated Debugging - Workspace seems to be different than the one given.

kt3072 — Wed, 09 Feb 2011 00:04:53 GMT

Well this doesn't come as a surprise, the workspace path wasn't recognized correctly. I had to put it in quotes. The following seems to find the workspace correctly:

cwide.exe -data "D:\Documents and Settings\ktimmler\workspace-1.8" X:\L1_Lte_Metro\dsp_code\make\.project -vmargsplus -Dcw.script="{D:\Documents and Settings\ktimmler\workspace-1.8\AutoBuild\runTest.tcl}"

Great! Thanks for your help.

Regards,

Killian