From: lfdebrux <lfdebrux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] micropython: update to 1.14
Date: Sat, 13 Feb 2021 17:46:50 +0100 [thread overview]
Message-ID: <20210213164650.upazZWd4jvVl3AHxnCIATs6jlWWMQHR4TyzF7i1CcGY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28708@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
New review comment by lfdebrux on void-packages repository
https://github.com/void-linux/void-packages/pull/28708#discussion_r575686867
Comment:
It doesn't look like they disable PIC; what's weird is that it works fine on x86_64-musl with PIE, but doesn't on armv5tel-musl, which as you say does point towards it being a bug in musl.
Here's a stacktrace from gdb
```
(gdb) start
Temporary breakpoint 1 at 0x90f0: file main.c, line 421.
Starting program: /usr/bin/micropython
Program received signal SIGSEGV, Segmentation fault.
0xb6fb68c0 in do_relocs () from /lib/ld-musl-arm.so.1
(gdb) backtrace
#0 0xb6fb68c0 in do_relocs () from /lib/ld-musl-arm.so.1
#1 0xb6fb6c88 in reloc_all () from /lib/ld-musl-arm.so.1
#2 0xb6fb900c in __dls3 () from /lib/ld-musl-arm.so.1
#3 0xb6fb867c in __dls2 () from /lib/ld-musl-arm.so.1
#4 0xb6fb569c in _dlstart () from /lib/ld-musl-arm.so.1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
```
next prev parent reply other threads:[~2021-02-13 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 18:25 [PR PATCH] " lfdebrux
2021-02-12 19:00 ` [PR REVIEW] " ericonr
2021-02-13 15:01 ` [PR PATCH] [Updated] " lfdebrux
2021-02-13 16:17 ` [PR REVIEW] " ericonr
2021-02-13 16:46 ` lfdebrux [this message]
2021-02-14 3:56 ` ericonr
2021-02-14 16:12 ` ericonr
2021-02-14 16:26 ` lfdebrux
2021-02-14 19:01 ` [PR PATCH] [Closed]: " ericonr
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=20210213164650.upazZWd4jvVl3AHxnCIATs6jlWWMQHR4TyzF7i1CcGY@z \
--to=lfdebrux@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).