From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] random segmentation fault during built
Date: Sun, 10 Jan 2021 17:04:05 +0100 [thread overview]
Message-ID: <20210110170405.29cf9095@gmx.net> (raw)
In-Reply-To: <CAEUhbmUnHYTOhirctT9EVphsys9PPwbvM5hkBKP7sVabnv1zmg@mail.gmail.com>
Hello Bin,
On Sun, 10 Jan 2021 21:57:45 +0800, Bin Meng <bmeng.cn@gmail.com> wrote:
> Hi,
>
> I see a random segmentation fault during the build of buildroot. For example,
>
> Makefile:13408: recipe for target 'install-pylibmountexecPYTHON' failed
> make[4]: *** [install-pylibmountexecPYTHON] Segmentation fault (core dumped)
> make[4]: *** Waiting for unfinished jobs....
>
> Type "make" for the 2nd time with nothing changed, or rarely a 3rd
> time, get a PASS build.
>
> This was observed by builds on Ubuntu 16.04 and Ubuntu 20.04 hosts.
> Any ideas of what could be wrong?
In case the errors are at random packages/locations (and succeed on iteration)
check your hardware and/or memory, see e.g. [1]...
Early versions of the AMD Ryzen CPU had heavy-load segfault bug, see [2]...
Regards,
Peter
[1] https://tldp.org/FAQ/sig11/html/index.html
[2] https://techreport.com/news/32459/amd-ships-revised-ryzen-cpus-with-a-compile-bug-fix/
>
> Regards,
> Bin
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-01-10 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 13:57 [Buildroot] random segmentation fault during built Bin Meng
2021-01-10 16:04 ` Peter Seiderer [this message]
2021-01-11 1:11 ` Bin Meng
2021-01-11 19:30 ` Peter Seiderer
2021-01-17 15:30 ` Bin Meng
2021-01-18 19:13 ` Peter Seiderer
[not found] ` <CAEUhbmVC0p2UBGEDg_k9LW-NBfWVdurzynDkZjTL76jA6iZ-3g@mail.gmail.com>
2021-01-18 19:22 ` Peter Seiderer
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=20210110170405.29cf9095@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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