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:
main(argc = 1, argv = 0xffbee6ac)
fdManager::process(0x1, 0x2, 0x1, 0xbc904, 0xe5800, 0xd5bb0)
casStreamOS::recvCB(0xe56f0, 0xe5800, 0xd9c9c, 0xd9c1c, 0xd5bb0, 0x1)
casStreamOS::processInput(0xe56f0, 0xd5bb0, 0xe56f0, 0xe56f0, 0xff1b9164,
0xffffffff)
casClient::processMsg(0xe571c, 0xbafd8, 0x4000, 0xffbee3ac, 0xe56f0,
0xdeb90)
casStrmClient::eventAddAction(0x4, 0xd5bb0, 0xe571c, 0xe5758, 0x4,
0xe5758)
casStrmClient::monitorResponse(0xe5708, 0x0, 0x30, 0x0, 0xe5830, 0xd5bb0)
0x0(0xf28c0, 0x1, 0xee6c0, 0x0, 0xee6c0, 0xee698)
Anyone have experience running the alarm handler with the portable server ?
Chris Timossi
- Replies:
- Re: alarm handler causes excas to core dump Ralph Lange
- RE: alarm handler causes excas to core dump Jeff Hill
- Navigate by Date:
- Prev:
Re: Agilent E2050A access from non-EPICS applications Marty Kraimer
- Next:
Re: alarm handler causes excas to core dump Ralph Lange
- 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:
XYCOM XVME 203 Counter Module w/ Quadrature Kristi Luchini
- Next:
Re: alarm handler causes excas to core dump Ralph Lange
- 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
|