My idea was to just start CB, open an executable file (which includes debug information) and CB shows up the source files involved in the executable (from the debug symbols), I can set breakpoints and start debugging. That's basically the functionality ddd provides under linux.
I found that about the same functionality can be achieved by using the "Attach to process" command, but that needs to get the pid of the process first. But, as I reported, no pop-up windows for variable contents were available and I had to set up breakpoints by using direct gdb commands ("break ns::function()"). Also I would miss the startup code of an application by attaching to it.
I was just too lazy to setup a real CB project, because my project (Qt on Windows, with self-created master Makefile), here has around 30 files. I think I'll try it; in addition I have seen that I can use my own Makefile with CB :-)
Regards,
Uli