Github messages for voidlinux
 help / color / mirror / Atom feed
From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: proot segfault on aarch64-musl
Date: Sat, 19 Sep 2020 16:15:31 +0200	[thread overview]
Message-ID: <20200919141531.zk1xFHdvxzsNICNBan36nuTLSJuWzStKhszu769AMSQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24918@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24918#issuecomment-695218626

Comment:
fdbf1993cb8a10136d7555d83ed15abdbe1f5c84 fixed the xorg-server issue. I've updated the top post to reflect that.

```
$ strace -o proot.strace.log proot -R /glibc/ /bin/sh
proot info: pid 5667: terminated with signal 11
```
[proot.strace.log](https://github.com/void-linux/void-packages/files/5249985/proot.strace.log)



```
$ strace --follow-forks -o proot.strace_follow_forks.log proot -R /glibc/ /bin/sh
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/usr/bin/sh"): Operation not permitted
proot info: It seems your kernel contains this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202161
To workaround it, set the env. variable PROOT_NO_SECCOMP to 1.
fatal error: see `proot --help`.
proot error: can't chmod '/tmp/proot-6019-aLbooi': No such file or directory
```
[proot.strace_follow_forks.log](https://github.com/void-linux/void-packages/files/5249988/proot.strace_follow_forks.log)



```
$ strace --follow-forks -o proot.strace_follow_forks_no_seccomp.log env PROOT_NO_SECCOMP=1 proot -R /glibc/ /bin/sh
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/usr/bin/sh"): Operation not permitted
proot info: possible causes:
  * the program is a script but its interpreter (eg. /bin/sh) was not found;
  * the program is an ELF but its interpreter (eg. ld-linux.so) was not found;
  * the program is a foreign binary but qemu was not specified;
  * qemu does not work correctly (if specified);
  * the loader was not found or doesn't work.
fatal error: see `proot --help`.
proot error: can't chmod '/tmp/proot-6504-hbEGIB': No such file or directory
```
[proot.strace_follow_forks_no_seccomp.log](https://github.com/void-linux/void-packages/files/5249991/proot.strace_follow_forks_no_seccomp.log)

  parent reply	other threads:[~2020-09-19 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  0:58 [ISSUE] " duncancmt
2020-09-19  3:50 ` fosslinux
2020-09-19 14:15 ` duncancmt [this message]
2020-09-19 14:47 ` Duncaen
2020-09-26 23:06 ` duncancmt-alt
2020-09-26 23:08 ` duncancmt-alt
2020-10-12  1:03 ` duncancmt
2020-10-12  1:03 ` [ISSUE] [CLOSED] " duncancmt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200919141531.zk1xFHdvxzsNICNBan36nuTLSJuWzStKhszu769AMSQ@z \
    --to=duncancmt@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).