Exception handling on macOS

[smaticka]

Describe the bug

Exception handling is unknown when running JEDI on the mac. See this example after a change was made to an ObsFunction (.cc file) in ufo:

2007: OOPS_TRACE[0] Variables::Variables
2007: Unknown exception: oops::HofX3D<FV3JEDI, UFO and IODA observations> terminating...
2007: Unknown exception: oops::HofX3D<FV3JEDI, UFO and IODA observations> terminating...

alternately, the same change made on Orion resulted in this readout (more verbose):

2259: OOPS_TRACE[0] Variables::Variables
2259: Exception: Error: YAML validation failed.
2259:   Location:      /observations/observers/0/obs filters/0/filter
2259:   Invalid value: "Variable Transform"
2259:   Cause:         unrecognized enum value
2259: Exception: oops::HofX3D<FV3JEDI, UFO and IODA observations> terminating...
2259: Exception: Error: YAML validation failed.
2259:   Location:      /observations/observers/0/obs filters/0/filter
2259:   Invalid value: "Variable Transform"
2259:   Cause:         unrecognized enum value
2259: Exception: oops::HofX3D<FV3JEDI, UFO and IODA observations> terminating...

To Reproduce
I'm not sure if this will reproduce it, but this is what I did:
built the jedi-bundle (internal) on the mac (see system) with spack-stack-1.5.1 with IODA converters turned on.
Received many warnings during build (see section below).

Expected behavior
The exception handling on the macOS should be more verbose (similar to the handling on Orion).

System:
mac M2 chip. macOS ventura 13.4. spack-stack-1.5.1

Additional context
When building the jedi-bundle (internal) on the mac, I received many warnings indicating this:
ld: warning: could not create compact unwind for...
From googling, it seems like that could lead to poor exception handling.

[smaticka]

@srherbener and @climbfuji

I tried rebuilding on my mac (complete new directory) with these lines uncommented in the jedi-bundle/CMakeList.txt file:

ecbuild_bundle( PROJECT eckit    GIT "https://github.com/ecmwf/eckit.git" TAG 1.24.4 )
ecbuild_bundle( PROJECT fckit    GIT "https://github.com/ecmwf/fckit.git" TAG 0.11.0 )

and then unloaded the modules just in case with:

module unload fckit/0.11.0
module unload eckit/1.24.4

I still receive numerous of the ld: warning (in initial description), and the exception handling did not change.

[srherbener]

@smaticka thanks for submitting this issue, and for testing the in-bundle build. Bummer that the in-bundle build didn't fix it - that would have been a great clue. The INFRA team will continue investigating this and will keep you posted.

[climbfuji]

@srherbener @smaticka Any update on this issue?

[smaticka]

@climbfuji I still get a lot of ld: warnings when building and the exception handling is not verbose as it is on Orion. Essentially appears to be the same problem even with recent builds.

[climbfuji]

I honestly think this issue should be in JCSDA-internal fv3-jedi or jedi-bundle ...

[smaticka]

@srherbener do you have a better idea of what repo might be the source of the problem? I can move the issue there.

[srherbener]

I think the exception messages are being thrown from eckit, but I doubt the problem we are seeing is coming from eckit.

What are you running when you see this symptom? Is it any particular ctest, or are you running an application (such as fv3jedi_hofx.x, or fv3jedi_var.x, etc)?