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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: PvData , PvAccess, Confusion with different hardware architectures |
From: | Michael Davidsaver via Tech-talk <[email protected]> |
To: | tech-talk <[email protected]> |
Date: | Mon, 8 Apr 2019 10:25:25 -0700 |
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