Every time I debug the game that I'm working on using kdevelop as the debugger I get a crash in kdevelop. More precisely, it aborts. There is no call stack.

This 'only' happens if I have breakpoints set, but I kinda need to have breakpoints set.

It may depend on the specific breakpoints -- after a half-dozen crashes I'm stopping for a bit.

Given that I'm not getting a call stack it's hard to make a useful bug report. Any thoughts on what to do?

You can run kdevelop through gdb:
gdb kdevelop
run

Then when it crashes, type "thread apply all bt" to get a backtrace similar to what drkonqui gives you.

Cheers,
Sven

Here https://techbase.kde.org/Development/Tu ... sh_reports you can find detailed instruction how to get backtrace when KDevelop or other KDE application crashes. Of course to be able get back trace you need to use KDevelop compiled with debug symbols.
Additionally you can run KDevelop in Valgrind.