On Mon, Sep 13, 2021 at 5:34 AM Robert Engels wrote:
>
> If the C code overruns a stack allocated variable couldn’t it easily corrupt
> the saved registers ?
Yes, that is another possible cause. Thanks.
Ian
> > On Sep 9, 2021, at 2:14 PM, Ian Lance Taylor wrote:
> >
> > On Thu, Sep 9, 2021
If the C code overruns a stack allocated variable couldn’t it easily corrupt
the saved registers ?
> On Sep 9, 2021, at 2:14 PM, Ian Lance Taylor wrote:
>
> 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
>
>
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
@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
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
@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
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
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:
