On 5/8/13 4:37 AM, Dirk Zimoch wrote:
> 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?
Hi, Dirk.
What version of EPICS Base is this?
What compiler was used to build for armv5teb?
Does the problem also occur when built with all compiler optimizations
disabled (i.e. -O0)?
Lewis
- Replies:
- Re: Timer Queue crash Dirk Zimoch
- References:
- Timer Queue crash Dirk Zimoch
- Navigate by Date:
- Prev:
Re: EPICS Extensions Compilation Errors Dirk Zimoch
- Next:
camonitor ignores format arguments for CHAR data Eric Norum
- 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:
Timer Queue crash Dirk Zimoch
- Next:
Re: Timer Queue crash Dirk Zimoch
- 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
|