Re: [go-nuts] Runtime panic identification

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

Re: [go-nuts] Runtime panic identification

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

Re: [go-nuts] Runtime panic identification

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

[go-nuts] Runtime panic identification

Hello Gophers, 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 internals. This Link