| 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: C++ Exceptions from CAC-UDP on exit |
| From: | Andrew Johnson <[email protected]> |
| To: | Jeff Hill <[email protected]> |
| Cc: | "'EPICS core-talk'" <[email protected]> |
| Date: | Thu, 14 Dec 2006 14:18:24 -0600 |
Jeff Hill wrote:
The root problem here I suspect is that DB CA link code does not have a shutdown procedure and therefore it is not destroying its CA context before the process exits. So when the process rundown starts and the resources that the UDP thread uses start to cease to exist then the UDP thread crashes.
If that is the problem the I agree we don't have much chance of fixing it. The strange thing though is that it's reporting an unknown C++ exception, so there is probably still something there that's able to catch whatever it being thrown. If we could modify the CAC-UDP task to expect that exception we could at least suppress the warning message, or convert it to something a little more innocuous.
What OS do you see this on? We might be able to attach with a debugger to get more detail, but I suspect that we will only see that the above suspicions are accurate.
I've only seen it on linux-x86 so far - I tried it on Solaris but it didn't occur there, and I've not run the tests on vxWorks yet.
- Andrew -- There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists -- Yosemite National Park Ranger