From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 49509@debbugs.gnu.org
Subject: bug#49509: libsigsegv fails to build on emulated aarch64 [core-updates]
Date: Sun, 11 Jul 2021 16:11:38 +0200 [thread overview]
Message-ID: <d6ed6b9f9275c1cb01f85fb42f069108371185f7.camel@telenet.be> (raw)
In-Reply-To: <875yxhbynf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
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.
If this is a bug in QEMU, then ideally that would be fixed in QEMU,
but I wouldn't know where to look.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-11 14:47 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 [this message]
2021-07-11 16:13 ` Ludovic Courtès
2021-09-30 2:40 ` Sarah Morgensen
2021-09-30 8:37 ` Efraim Flashner
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=d6ed6b9f9275c1cb01f85fb42f069108371185f7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49509@debbugs.gnu.org \
--cc=ludo@gnu.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.
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.