Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] xserver_xorg-server-1.15.1 crash on RaspberryPi when compiled with gcc-4.9
Date: Tue, 8 Jul 2014 00:02:07 +0200	[thread overview]
Message-ID: <20140708000207.272e4d2f@free-electrons.com> (raw)
In-Reply-To: <trinity-e2cf4efe-9b52-4b1c-a42e-28a15bb2f616-1402178338808@3capp-gmx-bs49>

Dear Peter Seiderer,

On Sat, 7 Jun 2014 23:58:58 +0200, Peter Seiderer wrote:

> running xserver (driver fbdev) on RaspberryPi crashes when compiled with gcc-4.9 (-Os).
> 
> Steps to reproduce (with buildroot-2014.05 release and additonal dillo package):

> Program received signal SIGSEGV, Segmentation fault.
> fbGlyphs (op=<optimized out>, pSrc=0x1, pDst=0x4, maskFormat=0x3b9d90, xSrc=0, ySrc=0, nlist=6, list=0xbefff490, glyphs=0x1)
>     at fbpict.c:140
> 140                 glyph = *glyphs++;
> (gdb) p glyphs
> $1 = (GlyphPtr *) 0x1

Thanks for the report. I wanted to let you know that I'm also seeing
the issue here, while testing the gtk-demo application under Xfbdev on
Qemu/ARM. I am also building with a gcc 4.9.x based toolchain, the
Linaro 14.05 toolchain. I haven't tested yet to rebuild with gcc 4.8.x
to see the difference.

Have you investigated the problem a bit more? Does it look like a
compiler issue?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-07-07 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 21:58 [Buildroot] xserver_xorg-server-1.15.1 crash on RaspberryPi when compiled with gcc-4.9 Peter Seiderer
2014-07-07 22:02 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-08 19:07 Peter Seiderer
2014-09-24 20:29 Peter Seiderer

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=20140708000207.272e4d2f@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox