Hi Georg,
OK, let's recognize it: diagnostics code is broken in the latest PCL versions. So please don't use it, for now. I have to make a deep review of all diagnostics code to fix it. Until then, please set diagnostics level to zero and use standard debugging techniques.
If the std::cout trickery is not nice for you (it is for me in a 95% of situations), I strongly recommend you create an Eclipse project for your module, then launch the PI Core application to start a GDB session from Eclipse. If you are accustomed to Visual Studio, then you'll find Eclipse's debugging interface very familiar. You have everything: breakpoints, conditional breakpoints, call stack, step-by-step execution, local symbols and so on. And if your code signals a system exception, GDB will stop execution and you'll find where it was thrown very easily.