From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Xorg crash
Date: Thu, 5 May 2016 11:33:13 -0300 [thread overview]
Message-ID: <572B59A9.2070602@zacarias.com.ar> (raw)
In-Reply-To: <1274ad69-0abb-26b0-b623-67de78c0274f@brickedbrain.com>
On 05/05/16 11:19, Luca Ellero wrote:
> Hi,
> I'm trying to get a minimal Xorg with Buildroot 2016.02 on Raspberry Pi
> 2, but the Xserver crashes as soon I launch dillo web-browser.
> I get the same crash if I launch fluxbox (or openbox or matchbox).
> I tried even on a iMX6 custom board but the same problem happens.
> The strange thing is that if I use only xterm and twm everything works
> correctly.
>
> I get:
>
> (EE) Segmentation fault at address 0x0
> (EE) Fatal server error:
> (EE) Caught signal 11 (Segmentation fault). Server aborting
> (EE)
> (EE) Please consult the The X.Org Foundation support
> at http://wiki.x.org for help.
> (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
> (EE)
> (EE) Server terminated with error (1). Closing log file.
>
> In attachment you can find the Xorg log and configuration file.
> Could someone please explain me what is going wrong.
>
> Thanks
> Regards
> Luca
Hi.
Try using BR2_OPTIMIZE_2=y and rebuild everything - the X server is
notoriously fragile when optimizing for size with certain toolchain
combinations/architectures.
Regards.
next prev parent reply other threads:[~2016-05-05 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 14:19 [Buildroot] Xorg crash Luca Ellero
2016-05-05 14:33 ` Gustavo Zacarias [this message]
2016-05-05 17:31 ` Thomas Petazzoni
2016-05-05 17:37 ` Gustavo Zacarias
2016-05-05 18:40 ` Peter Korsgaard
2016-05-06 6:20 ` Peter Seiderer
2016-05-06 6:54 ` Luca Ellero
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=572B59A9.2070602@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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