On Mon, Dec 26, 2022 at 10:56 AM Nikhilesh Susarla
wrote:
>
> So the SigPanic() captures the "_SIGSEGV" and then panics the whole program
> right?
It depends on precisely what you mean by that. SIGSEGV is marked with
the SigPanic flag in runtime/sigtab_linux_generic.go or whatever is
the equiv
So the SigPanic() captures the "_SIGSEGV" and then panics the whole
program right?
On Monday, 26 December 2022 at 23:49:12 UTC+5:30 Ian Lance Taylor wrote:
> On Mon, Dec 26, 2022 at 9:49 AM Nikhilesh Susarla
> wrote:
> >
> > https://play.golang.com/p/xpuit5lh9hh
> >
> > An array out of bounds
On Mon, Dec 26, 2022 at 9:49 AM Nikhilesh Susarla
wrote:
>
> https://play.golang.com/p/xpuit5lh9hh
>
> An array out of bounds throws panic at runtime.
>
> How does the internal runtime know that we are accessing the memory which we
> are not allocated? Interested in knowing more depth of the inte
Thanks Ian! Removing UPX solved the problem.
On Tue, Mar 15, 2022 at 9:25 PM Ian Lance Taylor wrote:
>
> On Tue, Mar 15, 2022 at 9:09 PM Stavros Filargyropoulos
> wrote:
> >
> > On an embedded 16 core arm device we have been observing infrequent runtime
> > crashes, with different signatures ev
On Tue, Mar 15, 2022 at 9:09 PM Stavros Filargyropoulos
wrote:
>
> On an embedded 16 core arm device we have been observing infrequent runtime
> crashes, with different signatures every time.
>
> One examples is this:
>
> unexpected fault address 0x6b6fc6da
> fatal error: fault
> [signal SIGSEGV:
Just because you print all of the parameters and they’re ok doesn’t mean there
isn’t any corruption. Sorry I can’t be of more help.
> On Nov 26, 2019, at 3:22 AM, 黃翔蔚 wrote:
>
>
> Hi Robert,
> Thanks for the explanation.
> There is only one function call from GO to CPP in the program.
> I p
Hi Robert,
Thanks for the explanation.
There is only one function call from GO to CPP in the program.
I printf all parameters in the CPP function.
There is no memory corruption inside.
If you have any other troubleshooting suggestions, I would appreciate it.
Walter
Robert Engels於 2019年11月26日星期二
It looks like the race detector outputs when it detects a race, not at program
end, so it doesn’t apply in your case.
So, I would look into cgo and other unsafe usages.
> On Nov 26, 2019, at 12:18 AM, 黃翔蔚 wrote:
>
> Hi Robert,
> I don't understand what you mean. Could you please explain more
Hi Robert,
I don't understand what you mean. Could you please explain more detail?
Thanks.
Walter
Robert Engels於 2019年11月26日星期二 UTC+8上午9時16分42秒寫道：
>
> I think with -race you want to exit before it crashes. After running a
> while. Can’t remember though. Check the docs.
>
> On Nov 25, 2019, at 7
I think with -race you want to exit before it crashes. After running a while.
Can’t remember though. Check the docs.
> On Nov 25, 2019, at 7:10 PM, 黃翔蔚 wrote:
>
>
> Hi lan,
> Thanks for your reply.
> I built the program with -race option. There is no news in crash dump.
> I will review cgo p
Hi lan,
Thanks for your reply.
I built the program with -race option. There is no news in crash dump.
I will review cgo portion again. Thanks again.
Walter
Ian Lance Taylor於 2019年11月26日星期二 UTC+8上午3時12分06秒寫道：
>
> On Mon, Nov 25, 2019 at 9:23 AM 黃翔蔚 >
> wrote:
> >
> > My program will get panic i
On Mon, Nov 25, 2019 at 9:23 AM 黃翔蔚 wrote:
>
> My program will get panic issue from time to time.
> I don't have procedure to reproduce this issue.
> So far, the issue is happen on 10/23, 10/25, 10/30, 11/14 and 11/22.
> In the last try, I capture packets by wireshark, it seems no packet incoming
12 matches
Mail list logo
