> You can’t add prints to a coredump and the run->add prints->compile->loop sucks a lot, especially if the bug is hard or slow to trigger. Yeah, but the core d

> You can’t add prints to a coredump and the run->add prints->compile->loop sucks a lot, especially if the bug is hard or slow to trigger. Yeah, but the core dump doesn't give you an answer on how the program ended up in failure state, does it?