Experimental Physics and Industrial Control System
Perhaps this information is related to your conversation. In my VM,
the printout of "g++ --version" is:
g++ (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks,
Rong
On Wed, Dec 20, 2023 at 6:40 AM Érico Nogueira Rolim
<erico.rolim at lnls.br> wrote:
>
> On 20/12/2023 06:34, Ralph Lange via Tech-talk wrote:
>
> On Wed, 20 Dec 2023 at 01:23, Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> wrote:
>>
>>
>>
>> Note that it is calling paramVal::getInteger in a try/catch block that explicitly catches the exception you are getting, ParamValNotDefined. So I don't understand why this is causing your program to terminate, rather than simply catching the error and return and error status.
>>
>>
>>
>> It seems like perhaps there is something different about the way C++ exception handling works with the linux-arm architecture? No one has ever reported this error before, but most people are using linux-x86_64.
>
>
> Just poking...
>
> Inside the ARM toolchain doc [1] I found that
>>
>> The ARM compilation tools fully support C++ exception handling. However, the compiler does not support this by default. You must enable C++ exception handling with the --exceptions option.
>
> Far too obvious to be the cause, is it?
>
>
> I don't think that it would be, because any reasonable Linux ARM system would be using GNU (or Clang) compilers, not the ARM compiler suite. "--exceptions" doesn't look like a GCC option either, and Linux userspace as a whole would be broken if built with "-fno-exceptions".
>
>
>
> Cheers,
> ~Ralph
>
> [1] https://developer.arm.com/documentation/dui0491/i/C-and-C---Implementation-Details/C---exception-handling#:~:text=The%20ARM%20compilation%20tools%20fully,%2D%2Dno_exceptions%20for%20more%20information.
>
>
>
> Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.
>
> Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.
- Replies:
- RE: quadEM-R7-0 ParamValNotDefined Mark Rivers via Tech-talk
- References:
- quadEM-R7-0 ParamValNotDefined Rong Huang via Tech-talk
- RE: quadEM-R7-0 ParamValNotDefined Mark Rivers via Tech-talk
- Re: quadEM-R7-0 ParamValNotDefined Rong Huang via Tech-talk
- RE: quadEM-R7-0 ParamValNotDefined Mark Rivers via Tech-talk
- Re: quadEM-R7-0 ParamValNotDefined Ralph Lange via Tech-talk
- Re: quadEM-R7-0 ParamValNotDefined Érico Nogueira Rolim via Tech-talk
- Navigate by Date:
- Prev:
Re: Steps for installing any EPICS Device Support module Érico Nogueira Rolim via Tech-talk
- Next:
Re: Steps for installing any EPICS Device Support module Eusebio Naif Al-Soliman Fuentes via Tech-talk
- 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:
Re: quadEM-R7-0 ParamValNotDefined Érico Nogueira Rolim via Tech-talk
- Next:
RE: quadEM-R7-0 ParamValNotDefined Mark Rivers via Tech-talk
- 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