XWayland on the RaspberryPI

[albert]

Thanks for the info Pekka,

Attached are weston-launch and xserver log files. df -h tells me /run/shm
has 75MB of free space. The crash is almost inmediate, I would think
xf-86-video-wayland delegates control at this point:

http://cgit.freedesktop.org/xorg/driver/xf86-video-wayland/tree/src/wayland.c#n497

And this is how I autogen the xserver - wayland branch:

./autogen.sh --disable-glx --disable-dri
           '--disable-dri2 --disable-dri3 --disable-libunwind
           '--disable-devel-docs --disable-docs
--disable-dependency-tracking
           '--disable-glx --disable-xinerama --disable-composite
--disable-record
           '--disable-present --disable-screensaver --prefix=$WLD

Thanks
Albert



2014/1/14 Pekka Paalanen <ppaalanen at gmail.com>

> On Tue, 14 Jan 2014 09:07:31 +0100
> albert <skarbat at gmail.com> wrote:
>
> > Greetings all,
> >
> > I am trying to make XWayland run on a Raspberry PI, so I am building
> > wayland/weston and the xserver xwayland branch from here:
> >
> >   git://anongit.freedesktop.org/xorg/xserver
> >
> > As well as the wlshm (now moved as wayland) driver: git://
> > anongit.freedesktop.org/xorg/driver/xf86-video-wayland
> >
> > When attempting to start a x11 app, the xserver effectively is
> > started, the wayland x driver loads successfully but when attempting
> > to "subload" the framebuffer driver, it segfaults. This fb driver has
> > been built as part of this same xserver.
> >
> > [  1056.806] (II) Loading sub module "fb"
> > [  1056.806] (II) LoadModule: "fb"
> > [  1056.808] (II) Loading /root/weston-bin/lib/xorg/modules/libfb.so
> > [  1056.811] (II) Module fb: vendor="X.Org Foundation"
> > [  1056.811]    compiled for 1.15.0, module version = 1.0.0
> > [  1056.812]    ABI class: X.Org ANSI C Emulation, version 0.4
> > [  1056.812] (==) Depth 24 pixmap format is 32 bpp
> > [  1056.813] (==) wayland(0): Backing store disabled
> > [  1056.813] (==) wayland(0): Silken mouse enabled
> > [  1056.815] (EE)
> > [  1056.815] (EE) Backtrace:
> > [  1056.815] (EE)
> > [  1056.816] (EE) Segmentation fault at address 0xe7933016
> > [  1056.816] (EE)
> > Fatal server error:
> > [  1056.816] (EE) Caught signal 11 (Segmentation fault). Server
> > aborting
> >
> > The contents of the xorg.conf file looks like so:
> >
> > Section "Device"
> >         Identifier "Device"
> >         Driver "wayland"
> > EndSection
> >
> > Any hints on what I might be missing would be greatly appreciated, or
> > even hints on how to debug this fault, as there is no timeframe to
> > gdb attach against the xserver before it dies.
>
> Hi Albert,
>
> that does not ring any bells for me. Could you attach the output of
> weston-launch (both stdout and stderr together), and the whole X log.
> Also check the free space in your XDG_RUNTIME_DIR, though I'd assume
> running out of space would cause SIGBUS rather than SEGV.
>
> I don't recall off-hand how to run the xwayland xserver under gdb,
> maybe someone else does? Might involve a bit of hacking.
>
>
> Thanks,
> pq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140114/47f99e4c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlaunch.log
Type: application/octet-stream
Size: 4627 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140114/47f99e4c/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.1.log
Type: application/octet-stream
Size: 7118 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140114/47f99e4c/attachment-0003.obj>