Re: [go-nuts] Plea for help diagnosing strange "signal: killed" issues in previously-working code

[Robert Engels]

Please clarify - does it work using the older versions of Go? On Mar 2, 2024, at 12:53 PM, Russtopia <rma...@gmail.com> wrote:  I have tried rebuilding with go1.18.6, go1.15.15 with no difference. On Sat, Mar 2, 2024 at 6:23 PM Robert Engels <reng...@ix.netcom.com> wrote: I would  be also try reverting the Go version and ensure that it continues to work. Other system libraries may have been updated. > On Mar 2, 2024, at 12:05 PM, Ian Lance Taylor <i...@golang.org> wrote: > > On Sat, Mar 2, 2024 at 9:59 AM Russtopia <rma...@gmail.com> wrote: >> >> Symptom: mysterious "signal: killed" occurrences with processes spawned from Go via exec.Cmd.Start()/Wait() > > The first step is to tell us the exact and complete error that you > see.  "signal: killed" can have different causes, and the rest of the > information should help determine what is causing this one. > > Ian > > -- > 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/CAOyqgcXR6hBSnGLjehwng%2BXp4QQ8ZznramEAZTmD%3D6tVwFirTg%40mail.gmail.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/8E4E2802-8E23-4427-ACA1-DBA30EBD8B30%40ix.netcom.com.