Michael Hudson-Doyle <michael.hud...@linaro.org> writes: > Michael Hudson-Doyle <michael.hud...@linaro.org> 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. What's happening is that when a signal -- SIGCHLD in this case >> -- is being handled, instead of being executed on the stack passed to >> sigaltstack, the signal is being handled on some *other* thread's stack, >> which unsurprisingly ends badly when a signal context object is smashed >> over whatever the original thread had put there.
I finally chased this down to (what at least I think is) a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16629 Cheers, mwh _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
