Re: errors in vxWorks-6.9/target/h(eader) files when building base 3.14.12.1

[Andrew Johnson <anj@aps.anl.gov>]

Hi Vesna,

On 2012-02-03 you wrote:
> 
> After building the base, I also built synApps 5.5 (without mca 7-0 because
>  mvme5100 BSP does not have BSP dma driver. My understanding is that I will
>  need your EPICS DMA driver to be able to use mca7 and SIS3820 scaler.

The MVME5100 board uses a Universe-2 chip.  A version of my DMA driver is 
described at http://www.aps.anl.gov/epics/tech-talk/2004/msg00124.php for that 
chip but I have a newer version for vxWorks 6.8 which I can send you if you 
want it.

> Just to mention, to build the epics base, in addtion to the 4 target/h
> files, I also modified libCom/osi/devLibVME.h line 306, from void
>  bcopyLongs(char *source, char *destination, int nlongs);
> to
>  void bcopyLongs(char *source, char *destination, size_t nlongs);

Interesting, in vxWorks 5.5 through 6.8 the nlongs argument is defined (in 
string.h) as an int, and we actually provide a version of the routine 
ourselves for RTEMS.  Can you confirm your new declaration above comes from 
the vxWorks 6.9 version of string.h?  I'll have talk to Michael Davidsaver and 
Eric Norum to work out what we do about that.

> NOT all the tests pass.
> The tests actually stop / terminate at:
> 
> ***** epicsTimeTest *****
> 1..195
> 0x24089b0 (tShell0): Unhandled C++ exception resulted in call to terminate

OK, that epicsTimeTest failure *is* a problem that will need fixing, and I 
don't think it's the last test run, so there are other tests that you haven't 
tried running yet.  Can you try attaching a debugger to find out what 
exception is getting thrown, where from, and why it's not getting caught?  If 
you want to try running the remaining tests first just comment out the line
    runTest(epicsTimeTest);
from the epicsRunLibComTests() routine in epicsRunLibComTests.c

It's interesting that epicsThreadPrivateTest succeeded, the epicsThreadPrivate 
code that it's checking uses the taskVar API that I thought Wind River were 
going to remove; maybe they only took it out of the SMP version.

> Before this "termination", 'only' one does not pass:
> 
> ***** epicsStdioTest *****
> 1..163

> not ok 156 - !fclose(stream)
> # fclose error: OK
> 
> not ok 157 - (stream = fopen(report, "r")) != NULL
> # 'report' could not be opened for reading:
>  S_ftpLib_REMOTE_SERVER_ERROR_550
> 
> Not sure how to go from here so any help or advice would be much
> appreciated.

This epicsStdioTest failure just means that when you ran it the working 
directory was not one that the IOC was allowed to write to, so this problem 
you can probably ignore.  To avoid it in the future make sure that you cd to a 
writable directory before starting the tests — I often forget to do that 
myself.  I'll add a diagnostic to the test explaining the usual failure cause.

- Andrew
-- 
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham