All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Random "Bus error" when building host-python
Date: Wed, 12 Dec 2012 23:54:06 +0100	[thread overview]
Message-ID: <20121212235406.768eb752@skate> (raw)

Hello,

If you have looked at the autobuilder results recently, there are some
host-python errors sometimes:

 http://autobuild.buildroot.org/results/b01a3c7233d53578961b74fb6ffb006782a43944/build-end.log
 Free Electrons build server, targeting mipsel

 http://autobuild.buildroot.org/results/5c59266f72f234ee9863e3d54270487b05af3612/build-end.log
 gcc14 build server, targeting powerpc

 http://autobuild.buildroot.org/results/3cf01dabafd47813c6fe11d0250e57ef667e8d95/build-end.log
 gcc14 build server, targeting powerpc

 http://autobuild.buildroot.org/results/7722a16700231a49b736fae697532013dfccfd2a/build-end.log
 Free Electrons build server, targeting arm

Every time, the build fail with a "Bus error". The log is not clear
enough to really understand what process is failing with a Bus error.

As you can see, the problem is not specific to one build machine, or
one target architecture (well, since it's in host package, it's kind of
obvious, but not the build machine fact).

And the thing is that those problems are not reproducible. If you take
the exact same commit ID of Buildroot, the exact same configuration, on
the exact same build machine, the problem may or may not produce
itself. I tried to reproduce it using one of those build
configurations, and he wasn't produced.

On the other hand, I did try to reproduce some other build
configuration that failed in the autobuilders, and instead of having
the error reported by the autobuilder web interface, I felt into the
"Bus error" problem in host-python. I just restarted the build (not
from scratch, simply restarted the build), and it went on without
failing into the "Bus error" problem. So it seems like the problem is
not in the generated code (re-executing the same code sometimes work
sometimes doesn't work).

Does anyone has ideas on how to further investigate this?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2012-12-12 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 22:54 Thomas Petazzoni [this message]
2012-12-13  1:06 ` [Buildroot] Random "Bus error" when building host-python Arnout Vandecappelle

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=20121212235406.768eb752@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.