nanogui: Thread: "wrong packet type" using threads in uclinux


[<<] [<] Page 1 of 1 [>] [>>]
Subject: "wrong packet type" using threads in uclinux
From: "Reynoso Luis-A19257" ####@####.####
Date: 4 Mar 2006 23:58:35 +0000
Message-Id: <4147ED8B92A864498825C07E53594E4AD8596D@az33exm20.fsl.freescale.net>

Hi there,

 

I'm using Nano-X under uCLinux in a ColdFire processor.

My project works fine in my PC (Nano-X + X11), but now I'm having some
problems with Nano-X in the uCLinux environment (FrameBuffer).

When calling some nano-X functions from a second thread, the application
fails and I get the following error message:

nxclient 36: Wrong packet type 0 (expected 53)

nxclient 26: Wrong packet type 0 (expected 22)

nxclient 36: Wrong packet type 1005 (expected 53)

nxclient 36: Wrong packet type 0 (expected 53)

 

These functions work perfectly when called outside the thread or when I
don't use threads.

 

Are you aware of any issues with nano-X in a multi-threaded environment?
Any workarounds?

 

Thanks in advance, 

Luis Reynoso

####@####.#### 

 

Subject: Re: [nanogui] "wrong packet type" using threads in uclinux
From: "Greg Haerr" ####@####.####
Date: 6 Mar 2006 21:20:15 +0000
Message-Id: <15b401c64163$bcfc31d0$0300a8c0@RDP>

> Are you aware of any issues with nano-X in a multi-threaded environment?

Of course, you need to have nano-X compiled with THREADSAFE=Y

> My project works fine in my PC (Nano-X + X11), but now I'm having some
problems with Nano-X in the uCLinux environment (FrameBuffer).
 
If it works with threads on the desktop with THREADSAFE=Y,
but not on the target, you may have a thread library issue.  See
the include/lock.h file for comments, make sure you're running
the right threads defines for your threads package.

Regards,

Greg

[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.