Hi Gabriel,
On Apr 7, 2021, at 2:54 AM, Gabriel Fedel wrote:
>
> After some tests I noticed that this change is causing a different behavior on one of my modules. Reading the discussion and the commit message I understood that this modification shouldn't change the base behavior but I think in my case it is.
>
> Is there some kind of configuration or test that I can do to force to avoid the inheritance?
Can you give us a bit more detail about the change that you’re seeing and how you have narrowed it down to this modification to the Priority Inheritance change? What epicsThread objects are you using, what Linux are you running it on, are you getting a deadlock, etc.
Thanks,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
- Replies:
- Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Gabriel Fedel via Core-talk
- References:
- Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Dirk Zimoch via Core-talk
- Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Gabriel Fedel via Core-talk
- Navigate by Date:
- Prev:
Build failed in Jenkins: epics-pvDatabase-win64 #898 APS Jenkins via Core-talk
- Next:
Build failed in Jenkins: 3.15-pvDatabase-win64 #354 APS Jenkins 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:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Gabriel Fedel via Core-talk
- Next:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Gabriel Fedel 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
|