Re: [go-nuts] BoringCrypto on arm64?

Not sure if this helps but there is also this repo that does things a little differently.. https://github.com/golang-fips/go -Eric http://www.google.com/profiles/eric.hubbard On Mon, Sep 26, 2022 at 12:02 PM Ian Lance Taylor wrote: > On Mon, Sep 26, 2022 at 2:51 PM Louisa Berger wrote: > >

Re: [go-nuts] BoringCrypto on arm64?

On Mon, Sep 26, 2022 at 2:51 PM Louisa Berger wrote: > > I've been using the BoringCrypto package, and would like to use it on > Graviton as well. I see from the caveat here > (https://go.googlesource.com/go/+/dev.boringcrypto/misc/boring#caveat ) that > BoringCrypto is only supported for

[go-nuts] BoringCrypto on arm64?

Hello, I've been using the BoringCrypto package, and would like to use it on Graviton as well. I see from the caveat here ( https://go.googlesource.com/go/+/dev.boringcrypto/misc/boring#caveat ) that BoringCrypto is only supported for GOOS=linux, GOARCH=amd64. Are there any plans to support

[go-nuts] Re: Go Get Issues

After I posted this on Friday I saw about adding .git to the end, and that didn't work. Then it started saying: repository.web.mycompany.com/st_nsres.git but package is repository.web.mycompany.com/st_nsres Or something like that. What I had

[go-nuts] Re: how to organise code with channels and error handling?

On Friday, September 23, 2022 at 10:24:36 AM UTC-4 joche...@gmail.com wrote: > Dear all, > > I am writing a program which processes data in stages. To structure the > code cleanly, I would like implement each stage as an individual function > and use channels to pass data between stages. > I

Re: [go-nuts] Invalid memory address of string object

On Mon, Sep 26, 2022 at 12:03 AM Bernd Fix wrote: > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x49388d] > Notice the "addr=0x0"? That's a nil pointer dereference. > > Can you show the definition of

Re: [go-nuts] importing Go is static linking or dynamic linking?

Actually, it depends on which std libs are used. https://www.arp242.net/static-go.html is a concise introduction. net and os/user normally prevent a static binary, unless build tags netgo and osusergo are used. On Monday, September 26, 2022 at 4:37:00 PM UTC+2 Ian Lance Taylor wrote: > On

Re: [go-nuts] importing Go is static linking or dynamic linking?

On Mon, Sep 26, 2022 at 7:22 AM Jessica Park wrote: > > When java... > can import .jar ... in this case, we call dynamic link.. > > How about golang? > > Is it dynamic linking or static linking? A pure Go program that does not use cgo will use static linking on most operating systems. A mixed

[go-nuts] importing Go is static linking or dynamic linking?

When java... can import .jar ... in this case, we call dynamic link.. How about golang? Is it dynamic linking or static linking? I need clear information. Thank you. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

Re: [go-nuts] Invalid memory address of string object

Also, this is consistent with your observation that calling peer.Key again returns a valid string. After the first call (returning the invalid string) the concurrent modification of p.str64 has finished and subsequent calls return the full value. Which is to say: Run your code under the race

Re: [go-nuts] Invalid memory address of string object

On Mon, Sep 26, 2022 at 9:03 AM Bernd Fix wrote: > Sure: > > // Key returns a string used for map operations > func (p *PeerID) Key() string { > if p == nil { > return "(nil)" > } > if len(p.str64) == 0 { > p.str64 = base64.StdEncoding.EncodeToString(p.Data) >

Re: [go-nuts] Invalid memory address of string object

No, p.Data is not nil - and the panic does not happen in the Key() method, but in the code from my first email.>Y< On 9/26/22 07:08, Andrew Harris wrote: could p.Data could be nil here? On Monday, September 26, 2022 at 12:03:20 AM UTC-7 Bernd Fix wrote: On 9/25/22 19:05, Kurtis Rader

Re: [go-nuts] Invalid memory address of string object

could p.Data could be nil here? On Monday, September 26, 2022 at 12:03:20 AM UTC-7 Bernd Fix wrote: > On 9/25/22 19:05, Kurtis Rader wrote: > > Insufficient information. Show us the panic > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation

Re: [go-nuts] Invalid memory address of string object

On 9/25/22 19:05, Kurtis Rader wrote: Insufficient information. Show us the panic panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x49388d] goroutine 100037 [running]:

Re: [go-nuts] Re: Invalid memory address of string object

On 9/25/22 19:06, 'Axel Wagner' via golang-nuts wrote: Another possibility is someone trying (and failing) to use unsafe to speed things up in a []byte/string conversion and accidentally converts a nil-slice. No unsafe in my own code, but I use a third-party library ("sdlcanvas") for

Re: [go-nuts] Re: Invalid memory address of string object

On 9/25/22 18:35, Jason Phillips wrote: Have your tried building and running your application with the race detector enabled[1]? You may have a data race. Thanks for the advice; that is possible although I have checked that access to all unsafe types like maps and arrays is controlled by