On Apr 7, 2011, at 11:46 AM, Jeremy Huddleston wrote: > On Apr 7, 2011, at 9:16 AM, Jeremy Huddleston wrote: > >> The "going crazy" is not a bug in quartz-wm. What version of the OS are you >> on? >> >> I'm curious how quartz-wm got into that state though. It's in an error >> handler, so it didn't like something it got from the server. > > So this is a bit confusing. The x_init_error_handler is only the error > handler for a short period of time *before* we enter the CFRunLoop. > Furthermore, it is set via XSetErrorHandler, not XSetIOErrorHandler ... so we > should never be calling into x_init_error_handler from XIOError, and we > should never be calling into that handler from within the CFRunLoop. > > This is a very puzzling backtrace...
The above sounds like "sample" misattributing a code address to the wrong symbol because the right symbol has been stripped. Unfortunately, it takes some sleuthing in the assembly code to figure out the real stack trace, if it's even possible. Regards, Ken _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
