On 03/16/2012 11:37 AM, Scott Moreau wrote:
On Fri, Mar 16, 2012 at 12:34 PM, Bill Spitzak <[email protected]
<mailto:[email protected]>> wrote:
weston-terminal is apparently crashing after about 12 characters are
typed. This is on the same system I had to turn EGL_DEPTH_SIZE off
on. I get the following messages:
Can you get a backtrace with gdb? For what it's worth, weston-terminal
works fine here on radeon.
disconnect from client 0x89c39e0
Error sending request: Broken pipe
Program received signal SIGABRT, Aborted.
0x0012e416 in __kernel_vsyscall ()
(gdb) where
#0 0x0012e416 in __kernel_vsyscall ()
#1 0x00350e71 in raise () from /lib/i386-linux-gnu/libc.so.6
#2 0x0035434e in abort () from /lib/i386-linux-gnu/libc.so.6
#3 0x00131452 in wl_proxy_marshal (proxy=0x81f7830, opcode=0) at
wayland-client.c:208
#4 0x0805130c in wl_buffer_damage (window=0x815afe0) at
/home/spitzak/install/include/wayland-client-protocol.h:367
#5 display_surface_damage (window=0x815afe0) at window.c:2250
#6 window_flush (window=0x815afe0) at window.c:787
#7 0x08051408 in idle_redraw (task=0x815b04c, events=0) at window.c:2118
#8 0x080538d0 in display_run (display=0x8059008) at window.c:3109
#9 0x0804f9c9 in main (argc=<value optimized out>, argv=0xbffff214) at
terminal.c:2392
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
