Forums

debug "step into" problem

Started by May 2, 2007
Hi Guys!

I have a problem with debugging c code in CCS v2. I can't "step
into" (sub)function codes, instead CCS steps into disassembly. Why
does CCS do this? Are there settings required so that I can step into
codes instead of stepping into disassemble window?

irishpat@mail2engineer.com wrote:
> Hi Guys! > > I have a problem with debugging c code in CCS v2. I can't "step > into" (sub)function codes, instead CCS steps into disassembly. Why > does CCS do this? Are there settings required so that I can step into > codes instead of stepping into disassemble window? >
That makes sense if the function you're stepping into is a library function (i.e. object code).
> That makes sense if the function you're stepping into is a library > function (i.e. object code).
Thanks Brian, It's not a library function. There's a source code for it. I had stepped through it before, but now, I can't. No big changes were made. Only deleted few commands like while loop instructions, nothing special.
More info:
The source file where I wanted to step into is in another project.
Let's call this project B. Project B is dependent on (main) project
A.
Project A has an executable file (.out) as output. I found out that
project B has .lib as output. I guess this is library file Brian was
referring to.
Does .out allow stepping through the source code? I tried generating
a .out
file for project B but it created an error when I built project A.
Also, I noticed
that in Build options, project A has linker, while project B has
Archiver. What
do I create\configure to allow stepping through source code in project
B?
By the way, I didn't write the code, just debugging it. Please help!

irishpat@mail2engineer.com wrote:
> More info: > The source file where I wanted to step into is in another project. > Let's call this project B. Project B is dependent on (main) project > A. > Project A has an executable file (.out) as output. I found out that > project B has .lib as output. I guess this is library file Brian was > referring to. > Does .out allow stepping through the source code? I tried generating > a .out > file for project B but it created an error when I built project A. > Also, I noticed > that in Build options, project A has linker, while project B has > Archiver. What > do I create\configure to allow stepping through source code in project > B? > By the way, I didn't write the code, just debugging it. Please help! >
In CCS you need to open the second project as a dependent project. I think you right click on the first project and there is a choice for "add dependent project". Note that this option did NOT work very well in CCS v2. It was improved in one of the more recent releases, perhaps CCS 3.1. You can get a 120 day eval of CCS 3.3: http://focus.ti.com/dsp/docs/dspsupportaut.tsp?sectionId=3&tabId=416&familyId=44&toolTypeId=30 By the way, my name is Brad not Brian.
Sorry, Brad.
I'm such a dumbass..

The second project is already a dependent project.
Thanks for the info. I have to use CCS v2.
Is there any thread or link that explains about this problem in CCS
v2?