From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Seiderer Date: Mon, 11 Jan 2021 20:30:57 +0100 Subject: [Buildroot] random segmentation fault during built In-Reply-To: References: <20210110170405.29cf9095@gmx.net> Message-ID: <20210111203057.07299bb3@gmx.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello Bin, On Mon, 11 Jan 2021 09:11:48 +0800, Bin Meng wrote: > Hi Peter, > > On Mon, Jan 11, 2021 at 12:04 AM Peter Seiderer wrote: > > > > Hello Bin, > > > > On Sun, 10 Jan 2021 21:57:45 +0800, Bin Meng 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/ > > Thank you. I checked the above 2 links and suspect it's not related. > > The issue happens on one Intel Xeon CPU with a Ubuntu 16.04 and one > Intel CORE i9 with a Ubuntu 20.04. The segmentation fault seems to > happen randomly during package "make install" phase. Back to the first question: random packages/locations or always at the same (or similar) location? Always some python (related) package? Which buildroot version? Mind to share your .config file? Mind to enable core-dump ('ulimit -c unlimited') and take a look at the core file? Regards, Peter > > Regards, > Bin