On 11/14/18 12:59 PM, Mark Rivers wrote:
> I am having 2 issues with the version of base-7.0 that I updated today.
>
>
>
> 1) Whenever I set a “busy” record to 0 in my drivers (e.g. areaDetector) I see this warning from modules/database/src/ioc/db/dbDbLink.c
>
>
>
> Warning: '13SIM1:cam1:AcquireBusy.PUTF' found true with PACT false
Ha, now Andrew can feel smug. I originally made this an assert().
FYI. 7.0.2 has a change to the way the PUTF, PACT, and RPRO fields interact.
The new protocol fixes an queuing issue when chaining multiple asynchronous records (via FLNK or OUT).
This warning is flagging a state which I didn't think should ever happen.
Though there is not any real harm if it does.
Can you run in a debugger and set a break point on the errlogPrintf() in question?
I'd like to know the exact stack trace (and thus DB link chain) involved.
https://code.launchpad.net/~epics-core/epics-base/+git/prop-putf/+merge/336468
> 2) When I run “make” in any App/op/ that automatically converts adl files to opi, ui, etc. I get these warnings:
>
> corvette:modbus/modbusApp/op>make
>
> /corvette/usr/local/epics-devel/base-7.0.1/configure/RULES_COMMON:18: warning: overriding recipe for target `show-makefile.../../configure/CONFIG'
I'll leave this one to Andrew.
- Replies:
- Re: Issues with latest version of base-7.0 Johnson, Andrew N. via Core-talk
- References:
- Issues with latest version of base-7.0 Mark Rivers
- Navigate by Date:
- Prev:
Jenkins build became unstable: epics-7.0 » linux32 #82 APS Jenkins via Core-talk
- Next:
Re: Issues with latest version of base-7.0 Johnson, Andrew N. via Core-talk
- Index:
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:
Issues with latest version of base-7.0 Mark Rivers
- Next:
Re: Issues with latest version of base-7.0 Johnson, Andrew N. via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|