Re: problem with sigaltstack on aarch64

Will Newton writes: > On 24 February 2014 03:15, Michael Hudson-Doyle > wrote: >> Michael Hudson-Doyle writes: >> >>> Michael Hudson-Doyle writes: >>> Hi all, Apologies if this is the wrong list, and for the somewhat vague description of my problem. I've been work

Re: problem with sigaltstack on aarch64

On 24 February 2014 03:15, Michael Hudson-Doyle wrote: > Michael Hudson-Doyle writes: > >> Michael Hudson-Doyle writes: >> >>> Hi all, >>> >>> Apologies if this is the wrong list, and for the somewhat vague >>> description of my problem. >>> >>> I've been working on porting Go (via gccgo) to aar

Re: problem with sigaltstack on aarch64

Michael Hudson-Doyle writes: > Michael Hudson-Doyle writes: > >> Hi all, >> >> Apologies if this is the wrong list, and for the somewhat vague >> description of my problem. >> >> I've been working on porting Go (via gccgo) to aarch64 and things have >> mostly been going well. However, under som

Re: problem with sigaltstack on aarch64

Michael Hudson-Doyle writes: > Hi all, > > Apologies if this is the wrong list, and for the somewhat vague > description of my problem. > > I've been working on porting Go (via gccgo) to aarch64 and things have > mostly been going well. However, under some circumstances, I'm seeing > crashes. W

problem with sigaltstack on aarch64

Hi all, Apologies if this is the wrong list, and for the somewhat vague description of my problem. I've been working on porting Go (via gccgo) to aarch64 and things have mostly been going well. However, under some circumstances, I'm seeing crashes. What's happening is that when a signal -- SIGC