Re: How to debug the xserver?
On 09/03/2012 11:32 PM, Bill Spitzak wrote: Thanks, it seems to be working now. cool. For X I'm getting a lot of black windows that only occasionally update, drawing pieces of their contents as those areas are drawn. I'm not seeing this here. What I was seeing is some glitches, like flashing, when windows are opened probably because of the opaque region (flashes are black so that's why I assume opaque region). I never had time to investigate the reason why though. Menus type of windows are easy to notice this. Also if you try to resize the top edge of the window it instead resizes as though you are moving the bottom edge in the opposite direction. same here. Should be easy to solve. There also isn't any close box or other toytoolkit decorations. same here. This is due the fact that xwm has to draw itself the decorations in opposing with toykit clients or other toolkits that you're used to. We're trying to change it now though making xwm a client. Tiago ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: How to debug the xserver?
On 08/31/2012 05:03 AM, Tiago Vignatti wrote: you need to update your xtrans library: http://lists.freedesktop.org/archives/wayland-devel/2012-August/005157.html I tried guessing at the name of the git repository but am not having much luck in figuring this out. Can you supply some more hints on how I get the updated xtrans library? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: How to debug the xserver?
On Mon, Sep 3, 2012 at 12:01 AM, Bill Spitzak spit...@gmail.com wrote: On 08/31/2012 05:03 AM, Tiago Vignatti wrote: you need to update your xtrans library: http://lists.freedesktop.org/**archives/wayland-devel/2012-** August/005157.htmlhttp://lists.freedesktop.org/archives/wayland-devel/2012-August/005157.html I tried guessing at the name of the git repository but am not having much luck in figuring this out. Can you supply some more hints on how I get the updated xtrans library? The repo is here git://anongit.freedesktop.org/xorg/lib/libxtrans http://cgit.freedesktop.org/xorg/lib/libxtrans ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: How to debug the xserver?
On 09/02/2012 11:06 PM, Scott Moreau wrote: On Mon, Sep 3, 2012 at 12:01 AM, Bill Spitzak spit...@gmail.com mailto:spit...@gmail.com wrote: On 08/31/2012 05:03 AM, Tiago Vignatti wrote: you need to update your xtrans library: http://lists.freedesktop.org/__archives/wayland-devel/2012-__August/005157.html http://lists.freedesktop.org/archives/wayland-devel/2012-August/005157.html I tried guessing at the name of the git repository but am not having much luck in figuring this out. Can you supply some more hints on how I get the updated xtrans library? The repo is here git://anongit.freedesktop.org/xorg/lib/libxtrans http://anongit.freedesktop.org/xorg/lib/libxtrans http://cgit.freedesktop.org/xorg/lib/libxtrans Thanks, it seems to be working now. For X I'm getting a lot of black windows that only occasionally update, drawing pieces of their contents as those areas are drawn. Also if you try to resize the top edge of the window it instead resizes as though you are moving the bottom edge in the opposite direction. There also isn't any close box or other toytoolkit decorations. I assume these are all known bugs but want to make sure they are not some problem with my version? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: How to debug the xserver?
On 08/31/2012 05:03 AM, Tiago Vignatti wrote: you need to update your xtrans library: http://lists.freedesktop.org/archives/wayland-devel/2012-August/005157.html That patch is not in the 1.12 branch I was told I needed to run. Can it be back-ported? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: How to debug the xserver?
Hi, On 08/30/2012 09:03 AM, Bill Spitzak wrote: The xserver crashes immediately on me in realloc. So far all the information I can get is a backtrace and event messages (this is just after attempting to launch xev which caused weston to run Xorg): I recompiled with --enable-debug but there is hardly any more information: [22:53:35.626] xfixes version: 4.0 [22:53:35.682] created wm [22:53:35.682] XCB_CREATE_NOTIFY (window 2097152, width 10, height 10, ours) [22:53:35.682] XCB_PROPERTY_NOTIFY: window 305, _NET_SUPPORTING_WM_CHECK: WINDOW/32, length 4 (value_len 1): huh? [22:53:35.683] XCB_PROPERTY_NOTIFY: window 305, _NET_SUPPORTED: ATOM/32, length 4 (value_len 1): _NET_WM_MOVERESIZE [22:53:35.683] XCB_CREATE_NOTIFY (window 2097153, width 10, height 10, ours) *** glibc detected *** /home/spitzak/install/bin/Xorg: realloc(): invalid next size: 0x0a30c9f0 *** === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x73e42)[0x5d0e42] /lib/i386-linux-gnu/libc.so.6(+0x7698f)[0x5d398f] /lib/i386-linux-gnu/libc.so.6(realloc+0xe7)[0x5d5347] /home/spitzak/install/bin/Xorg(ListenOnOpenFD+0xf0)[0x81c27c0] /home/spitzak/install/lib/xorg/modules/extensions/libxwayland.so(+0x21a3)[0x8411a3] /usr/lib/i386-linux-gnu/libffi.so.6(ffi_call_SYSV+0x1a)[0xa7135a] /usr/lib/i386-linux-gnu/libffi.so.6(ffi_call+0x6f)[0xa7108f] /home/spitzak/install/lib/libwayland-client.so.0(+0x4b03)[0xe8bb03] /home/spitzak/install/lib/libwayland-client.so.0(wl_display_iterate+0x1a6)[0xe8a0b6] /home/spitzak/install/lib/xorg/modules/extensions/libxwayland.so(+0x244b)[0x84144b] /home/spitzak/install/bin/Xorg(WakeupHandler+0x65)[0x807aae5] /home/spitzak/install/bin/Xorg(WaitForSomething+0x1a5)[0x81bd775] /home/spitzak/install/bin/Xorg[0x8076702] /home/spitzak/install/bin/Xorg[0x80643aa] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x5764d3] /home/spitzak/install/bin/Xorg[0x80646d9] === Memory map: 0011-0013a000 r-xp 08:01 4325425 /lib/i386-linux-gnu/libm-2.15.s... you need to update your xtrans library: http://lists.freedesktop.org/archives/wayland-devel/2012-August/005157.html Any ideas on how to perhaps get the x server running in a debugger? I tried changing the launch line to gdb --args Xorg ... but it did not work because it appears the tty is disconnected. Since this is memory corruption it may be that running valgrind might find something? In general we attach Xorg process in gdb (e.g sudo gdb -p `pidof /home/tiago/install/bin/Xorg`), but it's a little bit more trickier for the case where Xorg is crashing in its start and you'd need two gdb. So start the first gdb, set a break point on Weston weston_xserver_handle_event and run the program; open a X app and gdb will stop on that function; you'll have to step line by line until X process is forked and once that happens you attach another gdb on that process; now you have one gdb on Xorg and another for Weston. Valgrind is not attachable OTOH and what we can do is start it Weston with --trace-children=yes Tiago ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
