I would simply use kill to send a signal that generates a core dump and exits. Make sure you have the shell and security settings setup to all this to happen.
> On Oct 31, 2022, at 9:55 AM, Steven Sokol <st...@stevensokol.com> wrote: > > I tried doing that and it did not seem to work: > > root@pi4cm1(rw):/# gcore -o ~/lockup.core 22022 > Unable to attach: program exited with code 1. > You can't do that without a process to debug. > The program is not being run. > gcore: failed to create /root/lockup.core.22022 > > The attempt somehow killed the process. > >> On Wednesday, October 26, 2022 at 10:03:30 AM UTC-5 Konstantin Khomoutov >> wrote: >> On Wed, Oct 26, 2022 at 08:45:00AM -0500, Robert Engels wrote: >> >> > Trigger a core dump then use gdb on the core file. >> >> Also, the gdb is usually shipped with the `gcore` helper which can attach to >> the specified PID and dump its core. >> > > -- > 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/75272721-b821-4081-af23-2c84147bfadcn%40googlegroups.com. -- 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/CC5D84DB-A09C-4A5D-91FE-1A52940CA018%40ix.netcom.com.
