Hello,
I have a problem using epicsTimerQueueActive.
When I create a time queue with epicsTimerQueueActive::allocate(true)
then release it with epicsTimerQueueActive::release() and after that
call epicsTimerQueueActive::allocate(true) again, I get a segmentation
fault due to access to address 0.
I see no crash if I do not call release().
Interestingly, I see this effect only on my armv5teb (aka xscale_be)
embedded Linux system, but not on x86 or on p2020 ppc (big endian, too).
All accesses are in the same thread (_main_) during device initialization.
This happens when I use StreamDevice with at least two records connected
to a non-existing asynOctet port.
Any ideas?
Dirk
- Replies:
- Re: Timer Queue crash J. Lewis Muir
- Navigate by Date:
- Prev:
RE: CSS 3.1.x PVManager / JCA ClassCastException Carcassi, Gabriele
- Next:
Two questions about CSS Geng, Zheqiao
- 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: CSS 3.1.x PVManager / JCA ClassCastException marcus . michalsky
- Next:
Re: Timer Queue crash J. Lewis Muir
- 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
|