Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Tue, 27 Sep 2011 10:04:12 +0200	[thread overview]
Message-ID: <1317110841.20688.12.camel@sven> (raw)

Hi,

we are using buildroot successfully for quite a while now and after I've
recently managed to bring our buildroot environment up-to-date with
current git, I've changed the gcc version from 4.3.6 to 4.6.1. That was
the only change to the config. The resulting image boots and some
services (syslogd, klogd, udevd, sshd) are up and running. I can log
into the system and the busybox tools I tried to far seem to work fine.
However lots of applications that used to run fine now immidiately die
with a segmentation fault:

# dbus-daemon 
Segmentation fault

# uuidgen
Segmentation fault

# sqlite3
Segmentation fault

# iperf
Segmentation fault

What could possibly be wrong here? Is there anything else I need to
change when changing the version of gcc?


Sven

             reply	other threads:[~2011-09-27  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  8:04 Sven Neumann [this message]
2011-09-27 21:35 ` [Buildroot] Segmentation faults after gcc update Thomas Petazzoni
2011-09-28  8:57   ` Sven Neumann
2011-09-28 14:44   ` Sven Neumann
2011-09-30  9:06     ` Sven Neumann
2011-09-30 19:59       ` Thomas Petazzoni
2011-09-30 20:35         ` Thomas Petazzoni
2012-02-20 10:37           ` Sven Neumann
2012-02-20 16:55             ` Thomas Petazzoni
2011-10-04  9:20         ` Sven Neumann
2011-09-27 21:36 ` Thomas Petazzoni
2011-09-28  9:18   ` Sven Neumann

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=1317110841.20688.12.camel@sven \
    --to=s.neumann@raumfeld.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox