Experimental Physics and
Industrial Control System

On 4/2/19 9:06 AM, Michael Davidsaver wrote:
> On 4/2/19 8:12 AM, Heinz Junkes via Tech-talk wrote:
>> Hi folks,
>>
>> I am running a PvData client on RTEMS on a MVME6100 (PPC) and I see a behaviour that I can't even classify:
> 
> Then I think we should try to isolate where in the stack the problem(s) are.
> There are a lot of different modules involved.

Heinz was able to isolate the issue (thank you Heinz!), which is a regression
in array (de)serialization by BE peers which I introduced while fixing alignment
faults on powerpc.

https://github.com/epics-base/pvDataCPP/issues/65

References:

PvData , PvAccess, Confusion with different hardware architectures Heinz Junkes via Tech-talk

Re: PvData , PvAccess, Confusion with different hardware architectures Michael Davidsaver via Tech-talk

Navigate by Date:

Prev: RE: asynMotor device support and the motor specific driver (asynMotorContorller) Mark Rivers via Tech-talk

Next: Re: asynMotor device support and the motor specific driver (asynMotorContorller) Allan Serra Braga Bugyi via Tech-talk

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: PvData , PvAccess, Confusion with different hardware architectures Michael Davidsaver via Tech-talk

Next: Splitting the motor module Peterson, Kevin M. via Tech-talk

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024