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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | IOC error message on camonitor disconnect |
From: | <[email protected]> |
To: | <[email protected]> |
Date: | Wed, 26 Jul 2017 17:24:58 +0000 |
Hi, I am seeing this using EPICS base 3.15.5 running on windows x64. I start softIOC.exe and then repeatedly connect to a PV with camonitor and then CTRL-C the camonitor, each time I see either: epics> CAS: request from 127.0.0.1:20272 => CAS: Missaligned protocol rejected CAS: Request from 127.0.0.1:20272 => cmmd=26209 cid=0x150008 type=14592 count=0 postsize=24885 CAS: Request from 127.0.0.1:20272 => available=0x0 N=1 paddr=0000000000000000 CAS: forcing disconnect from 127.0.0.1:20272 epics> or A call to 'assert(size <= ntohs ( pMsg->m_postsize ))' by thread 'CAS-client' failed in ../../../src/ioc/rsrv/caserverio.c line 357. Dumping a stack trace of thread 'CAS-client': [ 000007FEEE71D565] [ 000007FEEE71D206] [ 000007FEEE714EF8] [ 000007FEED1A6AD5] [ 000007FEED1AC21B] [ 000007FEED1AC29B] [ 000007FEED1AAF1C] [ 000007FEED1AAAE5] [ 000007FEEE7177F1] [ 000007FECEB3B0A8] [ 000007FECEB3AD11] [ 00000000771459CD] [ 000000007727A561] EPICS Release EPICS R3.15.5. Local time is 2017-07-26 16:38:50.636232257 GMT Daylight Time Please E-mail this message to the author or to [email protected] Calling epicsThreadSuspendSelf() Thread CAS-client (000000000281A040) suspended It looks similar to the message reported in
http://www.aps.anl.gov/epics/tech-talk/2016/msg01828.php If I break into the program at the point of the assert I see the following details: size = 56 *pMsg m_cmmd=256 m_postsize=6144 m_dataType=5120 m_count = 256 m_cid = 16777216 m_available = 16777216 We only recently updated to 3.15.5 and I didn’t remember seeing such messages before, so I connected to a machine still running 3.14 and confirmed that I don’t get any errors reported for the same test on 3.14.12.6.
Regards, Freddie |