On Tue, Oct 13, 2015 at 03:23:12PM +0200, Joaquim Duran wrote:
> This is the backtrace but not much information is provided:
>
> Starting program: /usr/var/lib/weston-fullscreen
> [Thread debugging using libthread_db enabled]
> [New Thread 0x40105000 (LWP 325)]
>
> Program received signal SIGSEGV
These are the debug traces of the application:
DM-37x# ./weston-fullscreen -w 800 -h 600
[346.819] -> wl_display@1.get_registry(new id wl_registry@2)
[3470006.899] -> wl_disp...@1.sync(new id wl_callback@3)
[3470013.399] wl_display@1.delete_id(3)
[3470014.620] wl_registry@2.global(1, "wl_com
This is the backtrace but not much information is provided:
Starting program: /usr/var/lib/weston-fullscreen
[Thread debugging using libthread_db enabled]
[New Thread 0x40105000 (LWP 325)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x40105000 (LWP 325)]
0x0008 i
Pekka,
Thanks for your information. I've compiled simple clients and I've
executed fullscreen clients:
DM-37x# ./weston-fullscreen
Segmentation fault
And finishes with a segmentation fault. I'll rerun with debug
information to provide more information.
2015-10-13 14:37 GMT+02:00 Pekka Paalanen
On Tue, 13 Oct 2015 14:26:21 +0200
Joaquim Duran wrote:
> Hello,
>
> We could execute the Weston compositor (using fbdev backend) in a
> terminal, we could execute the weston-info client and it prints
> information, however when we execute the weston-terminal client, it
> couldn't open a window
Hello,
We could execute the Weston compositor (using fbdev backend) in a
terminal, we could execute the weston-info client and it prints
information, however when we execute the weston-terminal client, it
couldn't open a window on the compositor.
We start the Weston compositor in a terminal:
mkd
