Re: Xlib : sequence lost (0x1718e > 0x71a0) in reply to 0x0!
Hi to all I have made separate display connection to Xserver for each thread but this is working fine sometimes not always .sometime it fail when i invoke the dialog . can anybody help me to resolve this issues . Thanks Each call to XOpenDisplay opens a new communication socket to > the X-server. Commands sent through this socket need to be serialized. > If you have two threads trying to send data at the same time through > the same socket they will corrupt each other's data. XInitThreads > enables a lock around the Xlib code that accesses the socket so > that only one thread can send data through the socket at a time. > This generally works fine except that if you pause one thread while > it is in Xlib and has already taken the lock, it will prevent any other > thread from entering Xlib and taking the lock. Separate display > connections for each thread are the solution to that. > > Mark. > > > On Wed, 1 Feb 2006 [EMAIL PROTECTED] wrote: > >> Hi >> u have given a good suggestion but I dont understand if the >> pausing thread block any other thread trying to use the >>Xlib with the same display connection then why it is working >> fine sometimes . >> Thanks >> >> Separate threads either need to use separate display >> > connections or you need to enable thread mutexes for a shared >> > connection (XInitThreads will enable Xlib's internal mutexes). >> > Note still, that pausing a thread while it's in Xlib can block >> > any other threads also trying to use Xlib with the same display >> > connection. You'd want to use separate display connections >> > for that. >> > >> >Mark. >> > >> > On Tue, 31 Jan 2006 [EMAIL PROTECTED] wrote: >> > >> >> Hi to all >> >> >> >> >> >> Iam building an kde Application When I pause the current pthread and >> >> invoke an dialog in another thread the following error is >> coming . >> >> >> >> Xlib : unexpected async reply >> >> Xlib :sequence lost (0x1718e > 0x71a0) in reply to 0x0! >> >> X Error : BadImplementation (server does not implement opertaion) 17 >> >> Major opcode : 20 >> >> MInor opcode : 0 >> >> Resource id : 0x759d1 >> >> The error is coming randomly , not always . >> >> Can any will help how to come out of this error . >> >> >> >> >> >> Thanks >> >> ___ >> >> Devel mailing list >> >> Devel@XFree86.Org >> >> http://XFree86.Org/mailman/listinfo/devel >> >> >> > ___ >> > Devel mailing list >> > Devel@XFree86.Org >> > http://XFree86.Org/mailman/listinfo/devel >> > >> >> ___ >> Devel mailing list >> Devel@XFree86.Org >> http://XFree86.Org/mailman/listinfo/devel >> > ___ > Devel mailing list > Devel@XFree86.Org > http://XFree86.Org/mailman/listinfo/devel > ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: X Error : BadLength (poly request too large or Internal Xlib lengh Error )16
[EMAIL PROTECTED] wrote: Hi to all Iam building an kde Application When I pause the current pthread and invoke an dialog in another thread the following error is coming . X Error : BadLength (poly request too large or Internal Xlib lengh Error )16 Major opcode : 18 Minor opcode : 0 Resource id : 0x2005375 This error is not coming always . Can any one help me to solve this problem . We just had this conversation about the problems with multithreading Xlib. Have you taken the suggestions that were already given? -- Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc.
Re: [PATCH] to comply using Linux-2.6.16-rc2
On Mon, 6 Feb 2006, Jeff Chua wrote: I make this patch in order to compile latest CVS source with Linux-2.6.16-rc2 XFree86 Version 4.5.99.20 Release Date: 23 January 2006 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.16-rc2 i686 [ELF] I know it would be nice to do that change in , but afraid it'll get shot down in lkml. Someone want to try? Please comment. Problems like this show up every so often. They are caused by directly using kernel headers to rebuild glibc. You are instead supposed to use "laundered" headers, such as the ones available at ... http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ ... among others. And, yes. If you bring this up on LKML, you will indeed be flamed. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +---+ | University of Alberta | | | Edmonton, Alberta | Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
X Error : BadLength (poly request too large or Internal Xlib lengh Error )16
Hi to all > Iam building an kde Application When I pause the current pthread and > invoke an dialog in another thread the following error is coming . > X Error : BadLength (poly request too large or Internal Xlib lengh Error )16 Major opcode : 18 Minor opcode : 0 Resource id : 0x2005375 This error is not coming always . Can any one help me to solve this problem . Regards Niranjan ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
