Problems with debugger

Hello Giovanni,
--- Giovanni Parodi <g...@yahoo.it> wrote:

Hello everybody, I have some problem debugging my C
code:
I have a C code compiled using the following options
-g -pr -fr"$(Proj_dir)\Debug" -d"_DEBUG" -mo -mv6400
--mem_model:data --consultant
I use fastrts64x library (setting this library as
the
first in the linker order).
I do not modify this library (so I don't recompile
it,
I don't know if this is ok, I use memory model far
and
RTS calls use memory model).
When I try to modify this subroutine (both on board
and on functional simulator) I have the following
problem:
stepping into a subroutine (which name is f()) works
until a certain level of the subroutine, then the
debugger "sends" me to the following line of the
string.h file.

Have you tried...
After you step in f() and get near [but definitely
before] the problem area, change your display to
'mixed mode'. This will show the asm statements and
when you step, use 'asm step' instead of 'C step'.
Don't worry about understanding the details of the asm
code until you 'go into the weeds'. The assembly code
that is being executed before [we don't know how much
before] the 'bad branch' may give clues as to what is
going on.
mikedunn

#if defined(_INLINE) || defined(_STRNCAT)
_OPT_IDEFN char *strncat(char *dest, const char
*src,
register size_t n)
In no place I use this subroutine in f() but,
looking
at the map file I can see the following rows:
8070e8e0 000000e0 o2cr_char_segment.obj
(.text:_f)
8070e9c0 000000e0 rts6400.lib : strncat.obj
(.text:_strncat)
I'm not able to figure out what happens, it seems
that
the obj code of f has not enough place, but I don't
understand how to solve this problem.
So I would like to know if someone had similar
problem
with CCS 3.1 and if I have to recompile rts and
fastrts..
Thanks a lot Giovanni
Chiacchiera con i tuoi amici in tempo reale! 

http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com