From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: [PATCH A or B] Fix for bug #853 - matchbox-panel segfaults, X becomes unusable
Date: Wed, 16 Mar 2011 14:47:01 -0700 [thread overview]
Message-ID: <4D812FD5.5050504@linux.intel.com> (raw)
The root cause of the matchbox-panel segfault is the same as for the
previous two bugs addressing the same issue:
o Bug 224 - [Netbook/emenlow] matchbox-panel segfault after X startup
o Bug 738 - matchbox-panel segfault after X startup
There apparently is a bug in gcc which results in the omission of some
code leading to the segfault on core2. The following flags resolve the
problem.
FULL_OPTIMIZATION = "-fexpensive-optimizations -frename-registers -O2
-ggdb -feliminate-unused-debug-types"
We can continue to patch each new machine's gtk+ recipe that is based on
atom-pc.conf, or we can just add the above to tune-atom.conf. I've
tested both on both the n450 and a Toshiba NB305 netbook, and each
solution is effective.
Chaging it in tune-atom.conf likely fixes other bugs we either haven't
solved yet or simply haven't hit. It is also much more invasive, and we
may not be willing to accept that this close to 1.0. The patches follow,
and we can include one or the other.
Preferences?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next reply other threads:[~2011-03-16 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 21:47 Darren Hart [this message]
2011-03-16 21:49 ` [PATCH A] n450: add optimization flags to gtk+ for n450 to avoid gcc core2 bug Darren Hart
2011-03-16 22:09 ` Darren Hart
2011-03-16 22:34 ` Darren Hart
2011-03-16 21:50 ` [PATCH B] atom-pc: work around gcc bug for core2 Darren Hart
2011-03-17 0:13 ` [PATCH A or B] Fix for bug #853 - matchbox-panel segfaults, X becomes unusable Richard Purdie
2011-03-17 0:15 ` Stewart, David C
2011-03-17 1:05 ` Darren Hart
2011-03-17 2:13 ` Yu Ke
2011-03-17 3:22 ` Darren Hart
2011-03-17 10:46 ` Richard Purdie
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=4D812FD5.5050504@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.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.
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.