Most of the steps have described in Davinci Wiki. But you probably face problems when debugging in CCS after loading symbols. I'd like to share some thing here.
I'll use video_copy.x64P as an example.
Sequence:
1. Linux: Please to ensure "Pkg.attrs.profile" in your "packge.bld" file is "debug" no matter in codecs or servers.
2. Linux: To recompile them (codecs and servers) and copy x64P executable file to corresponding position (for example: /home/usracc/workdir/filesys/opt/dvevm/).
3. Linux to Windows: To copy codecs and servers folder from Linux to Windows (for example: to copy videnc_copy and viddec_copy and video_copy to windows)
4. Windows: After loading symbols (here I suppose that you've read Davinci Wiki about debugging codec in CCS), you must open an project of codec server (for example: servers.video_copy.pjt),
and then add source file (videnc_copy.c or viddec_copy.c) under the project.
Now, you can set your break point at code line in the source file instead of just at the beginning of every brackets.
If you do not open server project in CCS while debugging (the fourth step), I think you'll find that F10 and F11 is invalid (only "shift + alt + F11" works well) while debugging in source file, and you can not set break points at any position of the sorce code line.
In my opinion, if you do not open server project, I think, what you debug is the assembly language.
I hope this will help the beginners for CCS and Codec. :)
Lorry.