http://bugs.winehq.org/show_bug.cgi?id=5161
------- Additional Comments From jasonspiro3+wine@gmail.com 2006-24-05 00:29 ------- I was exploring http://en.wikipedia.org/wiki/X_Window_core_protocol and found some useful tips linked from there.
It seems Xlib synchronous mode would make it easier to track this bug down. According to http://www.rahul.net/kenton/perrors.html#Synchronization all we need to do is set the *synchronous application resource in our resource database, and then our app would die immediately as the failed X request was issued.
Another option might be to use xscope, which can monitor both X11 events and requests. See http://koala.ilog.fr/ftp/pub/xot.README for details.