[go-nuts] Re: 64 Tiny Algorithmic Puzzles in Go

qiulaidongfeng, A simpler, solution: https://go.dev/play/p/gLY7O_hwyxI peter On Saturday, March 2, 2024 at 8:25:33 PM UTC-5 qiulaidongfeng wrote: > I wrote a correct one, as shown here: > https://go.dev/play/p/IDJP_iIsGDE > > On Sunday, March 3, 2024 at 1:42:51 AM UTC+8 BUGFIX 66 wrote: > >> h

[go-nuts] Re: 64 Tiny Algorithmic Puzzles in Go

I wrote a correct one, as shown here: https://go.dev/play/p/IDJP_iIsGDE On Sunday, March 3, 2024 at 1:42:51 AM UTC+8 BUGFIX 66 wrote: > https://BUGFIX-66.com > > Solve each puzzle by making a tiny change to a short piece of Go code. > Edited code is compiled and tested on the host server. > Each

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

Glad you figured it out. Not certain how requests could crash a process like… I think you’d be better off configuring a maximum heap size rather than having the OOM killer kick in On Mar 2, 2024, at 3:50 PM, Russtopia wrote:SOLVED!Thank you all for the helpful suggestions. Although it has turned

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

SOLVED! Thank you all for the helpful suggestions. Although it has turned out to be something totally different, and a teachable lesson in web app design... This go tool of mine has a very simple web interface with controls for a set of jobs on the main page. The jobs on this list can be run, vie

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

My recommendation is run your program under the control of `strace`. The simplest way to do that is to rename the current program you're launching by adding something like a ".orig" extension. Then create a script with the name of the program containing this: #!/bin/sh exec strace -o /tmp/strace.o

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

I’m guessing some other library or package you installed has corrupted your Linux installation. Sadly, my suggestion would be a fresh install of Linux. On Mar 2, 2024, at 1:58 PM, Russtopia wrote:It no longer does.. so it suggests to me there's something external that has changed, but I have no c

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

.. I should add that I have often completely restarted the go program during testing here, so I don't think it could be a case of some long-term 'leak' in the go tool's own code since it's been relaunched and doesn't have any big 'state' to restore or anything. On Sat, Mar 2, 2024 at 7:57 PM Russt

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

It no longer does.. so it suggests to me there's something external that has changed, but I have no clue as to what that might be -- as the process being started by my go tool will run just fine from a shell. And, it *does* run fine on my laptop (which granted is beefier, but again this server was

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

Please clarify - does it work using the older versions of Go?On Mar 2, 2024, at 12:53 PM, Russtopia 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 wrote:I would  be also try reverting the Go version an

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

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 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 La

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

Hi, I tried outputting the value of werr.(*exec.ExitError).Stderr, but it's empty. Outputting all of werr.(*exec.ExitError) via fmt.Printf("[job *ExitError:%+v]\n", werr.(*exec.ExitError)) ..gives merely [job *ExitError:signal: killed] On Sat, Mar 2, 2024 at 6:04 PM Ian Lance Taylor wrote:

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

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 wrote: > > On Sat, Mar 2, 2024 at 9:59 AM Russtopia wrote: >> >> Symptom: mysterious "signal: killed" occurrences

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

On Sat, Mar 2, 2024 at 9:59 AM Russtopia 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 t

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

Hi all, Symptom: mysterious "signal: killed" occurrences with processes spawned from Go via exec.Cmd.Start()/Wait() Actors: 'Server': Intel i5, running Funtoo 1.4 - 4GB RAM, 4GB swap 'Laptop': Intel Core i7 9thGen, running Devuan Chimaera - 15GB RAm, 15GB swap A quite small -- ~900 lines of cod

[go-nuts] c-shared library for Aix

I have written multiple c-shared libraries code in golang for Windows, Linux, MacOS . I am using GCC cross compiler for the same. This code is running fine in production without any issue since last 3 years. But, we have recently got a requirement to compile the same thing for AIX/PowerPC but I

[go-nuts] 64 Tiny Algorithmic Puzzles in Go

https://BUGFIX-66.com Solve each puzzle by making a tiny change to a short piece of Go code. Edited code is compiled and tested on the host server. Each puzzle is a useful little algorithm or idea. Unfortunately, most users can't solve puzzle #3 and give up. Enjoy. -- You received this message b