Created attachment 1389928 [details] ps core file Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. x86_64: docker image load -i /path/to/Fedora27-aarch64-image 2. docker container create -ti <IMAGE_ID> bash 3. docker container start <CONTAINER_ID> 4. docker exec -ti <CONTAINER_ID> bash 4.2 dnf install procps 4.3 ps or top Actual results: SEGV Expected results: NO SEGV Additional info:
It's probably best taken to the upstream bug tracker, but please can you turn the core file into a stack trace. The core file is no use at all to us.
(In reply to Richard W.M. Jones from comment #1) > It's probably best taken to the upstream bug tracker, but > please can you turn the core file into a stack trace. The > core file is no use at all to us. Thanks for the reply. It happens while trying to execute aarch64 code inside a docker container, on a x86_64 CPU -- qemu-aarch64-static is involved as the binary translator. Currenly, only `ps' and `top' are crashed, other binaries work fine. On the other side, the coredump is truncated (though `ulimit -c unlimited` is tried) Also gdb doesn't work since qemu-aarch64-static will not emulate ptrace() syscall. I do find a similar (fixed) bug about `ps SEGV with qemu-*-static': https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/1254672, which points to quite an old version of qemu. I'll seek help from the upstream
I guess this maybe a bug in procps-ng: I tried to extract the binraries from ubuntu artful(https://launchpad.net/ubuntu/+source/procps/2:3.3.12-1ubuntu2/+build/10452812), and injected them into aarch64 image of fedora27, SEGV is gone for ps/top. Attachment 'procps.tar.xz' contains the extracted binraries.
Created attachment 1391900 [details] procps.tar.xz which contains extracted binraries from https://launchpad.net/ubuntu/+source/procps/2:3.3.12-1ubuntu2/+build/10452812
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days