Archaeologist,
I just read that and it was the problem of resolving overriding function definitions that I was looking for. Thanks.
Another question is on source file:
If there is only library but not the source, then debugging operations trying to access the source, such as "step into", would cause CCS reporting error that the source cannot be accessed. However, if both
- libA.lib
- libA.c
exist under the project folder, but they contain different versions of functions, and per command line specification linker actually resolves to libA.lib, the library file, but the original source file for libA.lib is not present. In this case, would "Step Into" jump into libA.c, incorrectly?
I guess this is actually a problem of how the IDE(CCS) or the linker keeps track of source information to distinguish the original source of the library, and another file of the same name? If there are time stamp as well as other identification, such as a hash number generated from the original source of the library, then it can recognize that the whether a source file with the same name is or is not the actual source; if such identification is not implemented, the it might get fooled (treat libA.c as source of libA.lib).
Is this correct?
Zheng
