On Mon, Oct 31, 2022 at 09:32:21AM -0700, Steven Sokol wrote: > I tried sending SIGABRT, but the process did not respond - continued > running in the runaway state. I can kill it with SIGKILL but that doesn't > generate a core. Can you suggest a specific kill command that will? Thanks!
Sending SIGKILL is worthless because this signal is never delivered to the target process: it's actually a request to the kernel to forcibly bring the process down without any extra fuss. To make the process drop the core, you should first make sure that this is allowed for the process - usually by running ulimit -c unlimited in the shell which starts the process (well, exactly how to make sure this ulimit parameter is set for your process heavily depends on how it starts up) and then sending a process any of the signals with "drop the core" default disposition - see the signal(7) manual page - and not handled by the process itself using the os/signal package). On Linux, SIGQUIT is typically the signal you want. And on a terminal (including virtual terminals such as Linux's virtual consoles, XTerm, GNOME Terminal, screen, tmux etc) sending of this signal is bound to Ctrl-\ by default. So, if you can run this program in the foreground mode - that is, from a shell session attached to a terminal, you can do ulimit -c unlimited /path/to/the/process # idenfity lockup # press Ctrl-\ to have the process sent the SIGQUIT -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/20221103091256.7dbi4nbcn3yxcprr%40carbon.
