YES.how to preserve the old one,i want use it to go back to golang,then
golang should recover it.
在 2018年3月30日星期五 UTC+8下午2:52:20,Ian Lance Taylor写道:
>
> On Thu, Mar 29, 2018 at 11:29 PM, hexun via golang-nuts
> > wrote:
> >
> > I really want to when call handlerSIGSEGV end, it will continue ba
On Thu, Mar 29, 2018 at 11:29 PM, hexun via golang-nuts
wrote:
>
> I really want to when call handlerSIGSEGV end, it will continue back to
> golang ,then golang will recover it.. Is there anyway?
Yes, there is a way. When you install your signal handler, preserve
the old one. After doing whatev
I really want to when call handlerSIGSEGV end, it will continue back to
golang ,then golang will recover it.. Is there anyway?
在 2018年3月30日星期五 UTC+8下午2:20:23,Ian Lance Taylor写道:
>
> On Thu, Mar 29, 2018 at 6:34 PM, hexun via golang-nuts
> > wrote:
> > func mustSendSIGSEGV(){
> > defer func
On Thu, Mar 29, 2018 at 6:34 PM, hexun via golang-nuts
wrote:
> func mustSendSIGSEGV(){
> defer func() {
> if err := recover(); err != nil {
> fmt.Print("enter recover 111")
> // logger.PrintPanicStack()
> }
> }()
> var r *Tes
func mustSendSIGSEGV(){
defer func() {
if err := recover(); err != nil {
fmt.Print("enter recover 111")
// logger.PrintPanicStack()
}
}()
var r *Test
r.Num = 0
}
i rewrite mustSendSIGSEGV like this。it is same as before.. ho
On Thu, Mar 29, 2018 at 8:48 AM, hexun via golang-nuts
wrote:
> From "The Go Programming Language" I see this:
>
> If the non-Go code installs any signal handlers, it must use the SA_ONSTACK
> flag with sigaction. Failing to do so is likely to cause the program to
> crash if the signal is receive