I’m not sure which language you’re working with, sometimes the CC environment has half-decent errors and for others there’s absolutely nothing to go on. It’s certainly frustrating if you’re used to being given a list of likely errors, their cause and line number or an interactive stepping tool but that doesn’t mean you can’t debug at all.
You’ll find similar guidance elsewhere but making small changes and testing it compiles/runs often can help as can using comments to edit out chunks of code to test what does and does not run. Printing/outputting anything and everything you’re not sure about can also help you pinpoint an issue. I’m sure there’s more such as breaking out the ducks if you search around but I’m sure you get the idea or already know this.
It might slow you down but such simple debugging techniques are something you’ll probably be using from now till the cows come home no matter how good your automated debugging tools are.