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

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

New issue by duncancmt on void-packages repository

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

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
`Void 5.7.0_1 aarch64-musl Unknown notuptodate rrDFFFFF`
(`notuptodate` because `xorg-server`>1.20.8_4 is broken)
* package:  
`proot-5.1.0_7`

### Expected behavior

I tried to set up a `glibc` chroot because I've been having big problems with programs segfaulting. (`flatpak`, `gdb`, `pavucontrol`)

```bash
sudo env XBPS_ARCH=aarch64 xbps-install --repository=http://alpha.de.repo.voidlinux.org/current/aarch64 -r /glibc -S base-voidstrap
proot -R /glibc/ /bin/sh
```

I expected to get a shell.

### Actual behavior

```
proot info: pid <REDACTED>: terminated with signal 11
```

See [attached log](https://github.com/void-linux/void-packages/files/5221846/proot.log) for `-v 9` output.

### Steps to reproduce the behavior

See above



             reply	other threads:[~2020-09-15  0:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  0:58 duncancmt [this message]
2020-09-19  3:50 ` fosslinux
2020-09-19 14:15 ` duncancmt
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24918@inbox.vuxu.org \
    --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).