Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7 Previous Document: 162) Can I make Xt or Xlib calls from a signal handler? Next Document: 164) What are these "Xlib sequence lost" errors? See reader questions & answers on this topic! - Help others by sharing your knowledge You'll typically get these errors if you are writing a multi-threaded application and are making X calls from more than one thread -- one of the more common new ways to introduce memory corruption into Xlib (using bogus pointers is another, as is mixing up XFree/XtFree/free calls. Even an operation as simple as XSendEvent can't be called from a second thread.). Prior to X11R6, X doesn't support multi-threading; check the X11R6 documentation for how to write a threaded application safely with X11R6 and later versions of X (including being sure to enable Xlib's multi-thread support). Common widget sets are also unsafe to use except from within one thread. The versions of Motif from OSF, for example, offer no support for multi-threading. User Contributions:Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7 Previous Document: 162) Can I make Xt or Xlib calls from a signal handler? Next Document: 164) What are these "Xlib sequence lost" errors? Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: faq%craft@uunet.uu.net (X FAQ maintenance address)
Last Update March 27 2014 @ 02:12 PM
|
Comment about this article, ask questions, or add new information about this topic: