From: Efraim Flashner <efraim@flashner.co.il>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 49509@debbugs.gnu.org
Subject: bug#49509: libsigsegv fails to build on emulated aarch64 [core-updates]
Date: Thu, 30 Sep 2021 11:37:36 +0300 [thread overview]
Message-ID: <YVV3UJQsUIDra25h@3900XT> (raw)
In-Reply-To: <86czoqu6p7.fsf@mgsn.dev>
[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]
On Wed, Sep 29, 2021 at 07:40:20PM -0700, Sarah Morgensen wrote:
> Hi all,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> > Hello,
> >
> > Maxime Devos <maximedevos@telenet.be> skribis:
> >
> >> Ludovic Courtès schreef op zo 11-07-2021 om 00:19 [+0200]:
> >>> Hi,
> >>>
> >>> Maxime Devos <maximedevos@telenet.be> skribis:
> >>>
> >>> > FAIL: stackoverflow1
> >>> > ====================
> >>> >
> >>> > qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> >>> > FAIL stackoverflow1 (exit status: 139)
> >>> >
> >>> > FAIL: stackoverflow2
> >>> > ====================
> >>> >
> >>> > Starting recursion pass 1.
> >>> > Stack overflow 1 missed.
> >>> > FAIL stackoverflow2 (exit status: 1)
> >>>
> >>> For now I worked around it by offloading this to a “real” machine
> >>> (overdrive1), where it builds fine. I wonder if there’s much we can do
> >>> regarding QEMU’s behavior here.
> >>
> >> Maybe detect if QEMU is used, and if so, don't run the test suite?
> >> Not really a ‘clean’ solution though, w.r.t. reproducibility,
> >> and I wouldn't know how to detect this.
> >
> > Yeah, I’d rather avoid that.
> >
> >> If this is a bug in QEMU, then ideally that would be fixed in QEMU,
> >> but I wouldn't know where to look.
> >
> > It could be that someone else on the intertubes stumbled upon that
> > issue, that’d be great. It could be that libsigsegv plays tricks that
> > don’t fare well with QEMU’s expectations, as in
> > <https://bugzilla.redhat.com/show_bug.cgi?id=1493304#c5>. We should ask
> > on bug-libsigsegv@gnu.org.
> >
> > Thanks,
> > Ludo’.
>
> (I just realized I never actually replied to this!)
>
> Configuring with "--disable-stackvma" seems to fix this. Doing this
> makes libsigsegv use a different heuristic for determining if a SIGSEGV
> was a stack overflow. I don't think it should impact functionality.
> Perhaps just apply that to aarch64 until there's a proper fix?
>
> This is probably a QEMU bug... I will try to report this to upstream
> QEMU when I can, as I can't find my notes on this right now.
>
I came across this on x86_64 when using our qemu-binfmt service when
building for powerpc-linux too, and I'm pretty sure powerpc64le-linux
and armhf-linux also. I haven't tried going the other direction, from
aarch64-linux and emulating x86_64/i686 to see if it happens there too.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-30 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 18:07 bug#49509: libsigsegv fails to build on emulated aarch64 [core-updates] Maxime Devos
2021-07-10 22:19 ` Ludovic Courtès
2021-07-11 14:11 ` Maxime Devos
2021-07-11 16:13 ` Ludovic Courtès
2021-09-30 2:40 ` Sarah Morgensen
2021-09-30 8:37 ` Efraim Flashner [this message]
2021-09-30 20:20 ` Ludovic Courtès
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=YVV3UJQsUIDra25h@3900XT \
--to=efraim@flashner.co.il \
--cc=49509@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.