> I've built a cas application starting with the excas example.
> The cas application core dumps when I run the alarm handler against it.
> It looks like the server library is trying to call a callback that doesnt
> exist but I cant tell. I just get the following stack trace:
> [...]
> Anyone have experience running the alarm handler with the portable server ?
Depending on how you use the alarm handler, it might try to acknowledge
alarms using Channel Access' special DBR types.
The GDD library that server tools use does not support application types
that correspond to the alarm acknowledgement CA messages.
The EPICS CA Proxy Gateway is the only CAS tool I know that supports
alarm operations. It is based on patches to the GDD and CAS libraries
that are not part of EPICS base. This is a non-desirable situation
created outside of my resonsibility that has been around for some years
now.
If you really, really want to see what is needed, you will have to fetch
the Gateway code, take a deep breath and look at it. (The Gateway has a
Tar file of the changes to EPICS base needed to do the ALH awareness.)
Hope this helps...
Ralph
ps. There's a link to the Gateway stuff on the EPICS Doc pages.
- References:
- alarm handler causes excas to core dump Chris Timossi
- Navigate by Date:
- Prev:
alarm handler causes excas to core dump Chris Timossi
- Next:
RE: alarm handler causes excas to core dump Jeff Hill
- 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:
alarm handler causes excas to core dump Chris Timossi
- Next:
RE: alarm handler causes excas to core dump Jeff Hill
- 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
|