Except the C++ "Core dumped" line is telling you it just wrote a file out with the full state of the program at the time of the crash, you can load it up and see where it crashed and then go and look at what every local variable was at the time of the crash.
Pretty sure you can even step backwards in time with a good debugger to find out exactly how you got to the state you're currently in.
gdb ./fuck r whereyou should get a complete stack trace (complete with values of some function arguments)
I know this is supposed to be humorous, but there's a reason why these languages can, and are doing what they're doing.
Core dumps are also worth learning about, they're really helpful if you understand them.
The ole' single C++ error turning into 600 lines of issues
puts me in mind of the old guru meditation error messages that popped up in the stone knives and bearskins era of computing.
LD_PRELOAD=libsegfault.so
or open core dump in gdb
