David C. Partridge wrote: > Specifically there are multiple (many, many) results looking like:
If you run "glxinfo", you'll find that they differ in terms of their GLX-specific properties (single-buffered or double-buffered, whether they have an accumulation buffer, and the number of samples for MSAA). > this is blowing the buffer for an application that uses xdpyinfo to > determine the display resolution to use. > Is there any fix for this problem? Use a larger (i.e. dynamically-allocated) buffer, or avoid making a copy (XGetVisualInfo() dynamically allocates the memory for the table and returns a pointer to it). -- Glynn Clements <gl...@gclements.plus.com> _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
