Re: Does EPICS Base support multi-thread on vxWorks 6.3?

[lorna.zhang@ni.com]

Andrew,

What is a munch file? Why doesn't my
bin\vxWorks-ppc603 folder include a vxTestHarness.munch file?

What is and how to link all the vxWorks
binaries into a single .munch file??

Let me know.

Thanks,

Lorna Zhang

From:	Andrew Johnson <anj@aps.anl.gov>
To:	lorna.zhang@ni.com
Cc:	"Jeff Hill" <johill@lanl.gov>, tech-talk@aps.anl.gov
Date:	05/05/2011 11:40 PM
Subject:	Re: Does EPICS Base support multi-thread on vxWorks 6.3?

---

Hi Lorna,

On Thursday 05 May 2011 04:41:57 lorna.zhang@ni.com wrote:
> Okay, now it seems the thread local storage epics implemented for
> vxWorks (in vxWorks\osdThread.c) is not working.
> 
> When I'm calling ca_context_create from a second worker thread in
a single
> process, I'll get the first context (which was created by the first
worker
> thread) returned by epicsThreadPrivateGet.

Can you try running the libCom test suite into your vxWorks system and
running 
it.  Instead of booting an IOC, load the bin/vxWorks-*/vxTestHarness.munch
file from Base for your architecture and run the command epicsRunLibComTests
to execute all of the tests, or for the epicsThreadPrivate facility alone
you 
would run the command epicsThreadPrivateTest.  If what you say above
is 
correct then that test will fail.

However I have an explanation if that test does not fail; I think the problem
you're seeing might be caused by loading two copies of libCom into the
IOC, 
which will definitely *not* work properly.  If your startup script
loads more 
than one .munch file, only the first one you load should be linked against
the 
$(EPICS_BASE_IOC_LIBS).  I usually recommend that you link all of
your vxWorks 
binaries into a single .munch file, but you can load multiple files as
long 
you're careful how you build them.

HTH,

- Andrew
-- 
An error is only a mistake if you don't learn from it.
When you learn something from it, it becomes a lesson.