A better way to debug Wayland

#1

Post by reddotX » Sun, Dec 23, 2018, 12:52 PM UTC

A better way to debug Wayland
community.ubuntu.com

Re: A better way to debug Wayland

#2

Post by secure » Sun, Dec 23, 2018, 2:57 PM UTC

Neat! It’s like xtrace (https://github.com/yuq/xtrace), but for Wayland.

Many years ago I wrote https://x11vis.org/ (it’s not that well-maintained, but works for me). It offers interactive filtering and a bunch of smarts that come in handy for debugging X11 wire protocol. Think Wireshark, but purpose-built for X11.

Re: A better way to debug Wayland

#3

Post by emersion » Sun, Dec 23, 2018, 5:53 PM UTC

secure wrote: post #2

Neat! It’s like xtrace ( https://github.com/yuq/xtrace ), but for Wayland. Many years ago I wrote https://x11vis.org/ (it’s not that well-maintained, but works for me). It offers interactive filtering and a bunch of smarts that come in handy for debugging X11 wire protocol. Think Wireshark, but purpose-built for X11.

Note that as opposed to xtrace and Wireshark, it isn't a proxy. It either parses libwayland's output or is a GDB plugin that integrates with libwayland.

Re: A better way to debug Wayland

#4

Post by emersion » Sun, Dec 23, 2018, 5:54 PM UTC

List of other tools to debug Wayland (scroll down to "Debugging tools"): https://wayland.freedesktop.org/extras.html

Re: A better way to debug Wayland

#5

Post by daniel_olivier » Sun, Dec 23, 2018, 10:20 PM UTC

I wish people would use something like LTTng, or some other solution that could "industrialize" logging/tracing, because every module or program, independant of language, potentially needs to be debugged/monitored, eventually.