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: | Re: R3.13.10 ca_event problem [sls] |
From: | Andrew Johnson <[email protected]> |
To: | Al Honey <[email protected]> |
Cc: | [email protected] |
Date: | Wed, 25 Jan 2006 14:52:44 -0600 |
Seems to me that the overflow affects taskWd in such a way that the memory corruption occurs at a low level and not from within the application code (two different memory maps on two different IOCs with two wildly different EPICS versions generating the same invalid instruction address). If taskWd simply attempts to suspend the offending task then does that mean the corruption occurs when the ring buffer overflow message is generated (perhaps something as simple as a malformed log message)?
- Andrew -- * * Matt Santos / / For a Brighter America * *