On 1 March 2016 at 13:00, Jakob Bohm wrote:
> As an alternative, could it be useful to look beyond the current
> glibc code and see if there is a way for qemu-user to provide the
> full set of Linux syscall provided facilities (including signals
> and calls), without having to reserve some for its
On 01/03/2016 12:37, Peter Maydell wrote:
On 1 March 2016 at 09:38, Hunter Laux wrote:
I was having trouble running golang on linux-user with an aarch64 target.
It turns out that snappy is written in Go. When I tried the xenial aarch64
preinstall image in qemu, Snappy was broken.
For some rea
On 1 March 2016 at 09:38, Hunter Laux wrote:
> I was having trouble running golang on linux-user with an aarch64 target.
>
> It turns out that snappy is written in Go. When I tried the xenial aarch64
> preinstall image in qemu, Snappy was broken.
>
> For some reason, it calls sigaction on all the
I was having trouble running golang on linux-user with an aarch64 target.
It turns out that snappy is written in Go. When I tried the xenial aarch64
preinstall image in qemu, Snappy was broken.
For some reason, it calls sigaction on all the signals.
I noticed do_sigaction in linux-user/signal.c
