PSA: Golang coredumps are (almost) completely useless because the Go runtime will catch SIGSEGV/SIGABRT and then *re-trigger the signal later*. This results in the coredump providing information about the Go runtime's handling of the signal not the cause of the signal.
Though at that point, you could just do the debugging in-situ. And note that delve (while it does have some nice features) does not appear to have the same behaviour as GDB wrt signals and pausing (and also has trouble running some programs like container runtimes as a debugger).