From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] rclone 1.53.3 segfaults on aarch64-musl
Date: Mon, 23 Nov 2020 15:01:24 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26638@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
New issue by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/26638
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 hold rrDDDDDFFFFF`
* package:
`rclone-1.53.3_1`
### Expected behavior
```$ rclone
Usage:
...
```
### Actual behavior
```$ rclone
Segmentation fault
```
### Steps to reproduce the behavior
See above
### Observations
Re-building rclone locally fixes the problem. Perhaps this is an issue with cross-compilation?
next reply other threads:[~2020-11-23 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:01 duncancmt [this message]
2020-11-23 14:08 ` ericonr
2020-11-23 14:09 ` ericonr
2020-11-23 14:12 ` duncancmt
2020-11-23 14:30 ` ericonr
2020-11-23 14:30 ` ericonr
2020-11-23 17:50 ` [ISSUE] [CLOSED] " ericonr
2020-11-23 17:51 ` ericonr
2020-11-23 21:39 ` duncancmt
2020-11-23 22:32 ` ericonr
2020-11-23 22:39 ` duncancmt
2020-11-23 22:41 ` ericonr
2020-11-23 22:52 ` ericonr
2020-11-23 22:53 ` ericonr
2020-11-23 22:54 ` ericonr
2020-12-11 1:19 ` sgn
2020-12-11 1:24 ` ericonr
2020-12-11 1:24 ` [ISSUE] [CLOSED] " ericonr
2020-12-11 1:26 ` 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-26638@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).