Re: [go-nuts] smtp.SendMail not using the from argument

It could be that I'm not using smtp.SendMail() correctly, which is why I posted it here. Thanks for your guess, though. On Thursday, September 9, 2021 at 2:31:11 PM UTC-6 rol...@gmail.com wrote: > Hello, > > Am Do., 9. Sept. 2021 um 20:19 Uhr schrieb Dean Schulze < > dean.w@gmail.com>: >

Re: [go-nuts] smtp.SendMail not using the from argument

Hello, Am Do., 9. Sept. 2021 um 20:19 Uhr schrieb Dean Schulze < dean.w.schu...@gmail.com>: > I'm sending emails with smtp.SendMail() via gmail. I set the from > argument to smtp.SendMail() to a different email address than my gmail > username, but the emails still get sent with the From: as my

[go-nuts] [security] Go 1.17.1 and Go 1.16.8 are released

Hello gophers, We have just released Go versions 1.17.1 and 1.16.8 minor point releases. These minor releases include a security fix according to the new security policy (#44918 ). The fix for CVE-2021-33196 can be bypassed by crafted inputs. As a result, the

Re: [go-nuts] Re: Debugging "fatal: morestack on gsignal"

On Thu, Sep 9, 2021 at 10:29 AM Varun V wrote: > > @Brian, We did not try that as the issue is happening with go 1.13.7 as well The "fatal: morestack on gsignal" error is more or less impossible. Some things that can cause it to happen are 1) C code calls sigaltstack, but the alternate signal

Re: [go-nuts] Re: Debugging "fatal: morestack on gsignal"

@Brian, We did not try that as the issue is happening with go 1.13.7 as well On Thu, 9 Sep, 2021, 10:48 pm Brian Candler, wrote: > Just a random thought, but have you tried 1.16 > with GODEBUG=asyncpreemptoff=1 ? The preemptive scheduling stuff was > introduced in 1.14 I believe. > > On

[go-nuts] smtp.SendMail not using the from argument

I'm sending emails with smtp.SendMail() via gmail. I set the from argument to smtp.SendMail() to a different email address than my gmail username, but the emails still get sent with the From: as my gmail address. Do I need to do something else to change the From: in the emails, or is gmail

Re: [go-nuts] Re: Debugging "fatal: morestack on gsignal"

Just a random thought, but have you tried 1.16 with GODEBUG=asyncpreemptoff=1 ? The preemptive scheduling stuff was introduced in 1.14 I believe. On Thursday, 9 September 2021 at 16:28:38 UTC+1 varun...@gmail.com wrote: > @Kurtis, Thanks for the reply. > > Yes. We upgraded to 1.16.5 due to

Re: [go-nuts] Re: Debugging "fatal: morestack on gsignal"

@Kurtis, Thanks for the reply. Yes. We upgraded to 1.16.5 due to this issue and had to revert back to 1.13.7 (over earlier working version) as we are frequently seeing these errors in 1.16.5. I looked into all the related issues on golang forums. We are not on NetBSD (We are on CentOS7.8) We

Re: [go-nuts] Re: Debugging "fatal: morestack on gsignal"

Googling "go morestack on gsignal" turns up quite a few reports. Some of which involved kernel bugs (e.g., https://github.com/golang/go/issues/19652) but most seem to involve SIGSEGV errors in non-kernel code; sometimes the Go runtime or stdlib (e.g., https://github.com/golang/go/issues/35235) and

[go-nuts] Re: Debugging "fatal: morestack on gsignal"

Minor update: a. The crash with "morestack on gsignal" happens to be independent of the kernel versions mentioned earlier b. We implemented a signal handler to catch SIGSEGV from CGO. That is not helping either c. From system audit logs, we can see the following message:

[go-nuts] Simplifying LLVM bitcode from gollvm

A Helloworld written in C++ is around 75 lines in LLVM IR. However, a Helloworld written in Golang compiled with gollvm is around 900/1000 lines of .ll file. I produced the LLVM IR with instructions from https://go.googlesource.com/gollvm/ I'm using LLVM11, so, older compatible commit of

Re: [go-nuts] Re: WASM Performance

Even when I remove all rendering and just run the Go WASM in a web worker, like this: const go = new Go(); WebAssembly.instantiateStreaming(fetch("web2600.wasm"), go.importObject).then((result) => { go.run(result.instance); }); The binary is still performing a long way