GDB can get you started:
$ gdb --help
This is the GNU debugger. Usage:
gdb [options] [executable-file [core-file or process-id]]
gdb [options] --args executable-file [inferior-arguments ...]
[snip extended docs]
So, you’ll invoke it like this:
gdb myprog core
GDB will then start in the usual way, but the state will be as if you’d stopped at a breakpoint. You can then use “print”, “examine”, “list”, “backtrace”, “up”, “down”, etc. to investigate what caused the crash.
In fact, you can use any GDB command except “continue”, “step”, “next”, or anything else that requires an actual running program.
4
solved How to analyse a coredump file of GDB [closed]