I suspect this is a NULL pointer access that happens in procps where it
isn't handling an error path that it's not expecting somehow (either a
syscall we're not implementing, or perhaps something like /proc not
being mounted in your chroot environment, or something about qemu's
emulation of some fi
qemu-powerpc-static on i386:
# ps
Invalid data memory access: 0x
NIP 0feb05e4 LR 0feb1440 CTR 0feb13f0 XER
MSR 6040 HID0 HF 6000 idx 0
TB
GPR00 0ffc178c 407fffa0 4083f720 0001
GPR04 29292929
Same thing with qemu-mips-static too by the looks of things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254672
Title:
ps segfaults with qemu-arm-static
To manage notifications about this bug go
** Description changed:
Host: Ubuntu Precise AMD64
- Guest: Debian Testing armhf
+ Guest: Debian Testing armhf (or armel)
After running a debootstrap for Debian testing/armhf and entering the
chroot, simply running "ps" causes a segmentation fault.
$ sudo qemu-debootstrap --arch=armh
** Also affects: qemu-linaro
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254672
Title:
ps segfaults with qemu-arm-static
To manage notifications about
