Experimental Physics and Industrial Control System
Subject: |
Re: VxWorks 6.7, MV5500 Re: EPICS R3.14.11, sequencer 2.0.12 crash on device support write error |
From: |
Andrew Johnson <[email protected]> |
To: |
[email protected] |
Date: |
Fri, 9 Jul 2010 10:03:48 -0500 |
Hello Kay,
On Friday 09 July 2010 07:51:33 Kasemir, Kay wrote:
>
> For the record, we found that our combination of VxWorks 6.7 and MV5500 BSP
> doesn't fully support C++ exceptions. The reported EPICS R3.14.11/sequencer
> 2.0.12 crash is not caused by problems in the code, but solely results from
> issues with the exception support.
I would be very interested to know whether the libCom/test/epicsExceptionTest
program detects this or not, and if not whether you could patch it so it does.
IIRC Ron Sluiter discovered a similar problem with C++ exceptions on the
target solaris-x86_64-gnu which was detected by that test routine; I'm
attributing that failure to gcc, building with the SunPro compiler on solaris-
x86_64 works fine.
You can run that test by loading bin/vxWorks-<cpu>/vxTestHarness.munch and
typing 'epicsExceptionTest'.
Thanks,
- Andrew
--
The best FOSS code is written to be read by other humans -- Harald Welte
- Replies:
- Re: VxWorks 6.7, MV5500 Kasemir, Kay
- References:
- VxWorks 6.7, MV5500 Re: EPICS R3.14.11, sequencer 2.0.12 crash on device support write error Kasemir, Kay
- Navigate by Date:
- Prev:
RE: linking to shared objects user libraries Mark Rivers
- Next:
Re: linking to shared objects user libraries J. Lewis Muir
- 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:
VxWorks 6.7, MV5500 Re: EPICS R3.14.11, sequencer 2.0.12 crash on device support write error Kasemir, Kay
- Next:
Re: VxWorks 6.7, MV5500 Kasemir, Kay
- 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