Re: USE of CA lib: problem using ca_array_put_callback with strings

[haquin <haquin@ganil.fr>]

Hi Andrew,

Of course, the test with the caput tells us that the problem is not in 
the example client program.

We've just realized that my IOC was running under VxWorks !
So I restarted the SAME IOC but under linux-x86 and then all is working 
correctly.
Here is the difference you are looking for, the problem occur under VxWorks.

If you are still interrested to know more about my IOC, Here is more 
about it:
we have a Waveform record using ASYN/MODBUS device support,
Some "GenSub", "ai" and "ao" records all using soft device support
=> the problem occur independently of the record type (under VxWorks only)

Regards.

Andrew Johnson a Ãcrit :
> Hi Christophe,
>
> On Friday 14 November 2008 10:34:16 haquin wrote:
>   
> > We tried with the command line, and we can reproduce the problem, here
> > is the result:
> > [haquin@accep1 haquin]$ caput -c LB-DIA-ALB-TST2:Read_16bits_Reg.DESC
> > "abcdefg"
> > Old : LB-DIA-ALB-TST2:Read_16bits_Reg.DESC It's 14-NOV-2008 16:52:23.04
> > New : LB-DIA-ALB-TST2:Read_16bits_Reg.DESC a
> > [haquin@accep1 haquin]$ caput LB-DIA-ALB-TST2:Read_16bits_Reg.DESC
> > "abcdefg" Old : LB-DIA-ALB-TST2:Read_16bits_Reg.DESC a
> > New : LB-DIA-ALB-TST2:Read_16bits_Reg.DESC abcdefg
> >     
>
> That is very interesting, and tells me that the problem is probably not in 
> that example client program.
>
> Tell me about the IOC that this PV resides on, and the record type and device 
> support of the record itself.  Does the problem also occur with other fields 
> or other record types?  Is it limited to this particular IOC, or this 
> architecture of IOC?
>
> I'm trying to find out what might be different about your installation and 
> IOC, because I am unable to replicate this behavior on a linux-x86 IOC here 
> using R3.14.9.
>
> - Andrew
>   

begin:vcard
fn:Christophe Haquin
n:Haquin;Christophe
email;internet:haquin@ganil.fr
tel;work:02 31 45 46 61
x-mozilla-html:FALSE
version:2.1
end:vcard