2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Possible Bug in 3.14.9 Access Security on mv2100 |
From: | Ralph Lange <[email protected]> |
To: | Jeff Hill <[email protected]> |
Cc: | "'EPICS core-talk'" <[email protected]>, "'Steven Hartman'" <[email protected]> |
Date: | Fri, 10 Aug 2007 09:58:01 +0200 |
Note that the setup of my original system was: vxWorks:Using the same 3.14.8.2. (optimized) client, the faulty behaviour (100%) appears with 3.14.9 (optimized) IOCs, and does not appear with 3.14.8.2 (optimized) IOCs.
Linux:Using the same 3.14.8.2 (optimized) client, the faulty behaviour (20%) appears with a 3.14.9 (optimized) soft IOC, and does not appear with a 3.14.8.2 (optimized) soft IOC.
Ralph Jeff Hill wrote:
More observations from Steven: Now, I just rebuilt all of base on linux with HOST_OPT=NO. Even stranger.Using optimized build on linux, caget failed with an unexpected read access error 19 out of 20 times just tested. Using non-optimized build on linux, caget failed 2 out of 20 times!This appears to be a major hint. I need to confirm that the behavior changed this way (as described above) when the CA client library's optimization level changes, and that during this experiment the IOC's optimization level was not changed. Jeff