A ticket which seems to cover the same problem: https://ghc.haskell.org/trac/ghc/ticket/11829 —Adam

On 4 Jan 2019, at 16:50, Bas van Dijk wrote:

On Fri, 4 Jan 2019 at 14:15, Gabor Greif wrote:

...

maybe some DWARF unwind tables are not correctly installed in OS X?

Hi Gabor, thanks, I will look into that.

...

Do intra-C++ exception catching work in your example?

Yes, I have a C++ executable foo[1] that links with libfoo that correctly catches the exception:

...

$(nix-build --no-link -A foo)/bin/test ... Whoops!

Since it's working in pure C++ I suspect it has something to do with how GHC calls either the C++ compiler or linker.

Bas

[1] https://github.com/basvandijk/darwin-cxx-exception-bug/blob/master/foo/test.... _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Are we talking about Haskell or linking/ calling c plus plus? If the latter, that’s more of a cabal issue I think? If you mean ghc build wise No. The unwind library only supports elf format. Which OS X does not use. Even that issue aside : ghc currently can’t build with any level of dwarf enabled on OS X, eg the system linker complains about exceeding some system section object format limit. I guess my point is : dwarf data for Haskell libraries on OS X have a few challenges between here and there. On Fri, Jan 4, 2019 at 9:29 PM Bas van Dijk wrote:

On Fri, 4 Jan 2019 at 23:46, Adam Sandberg Eriksson wrote:

...

A ticket which seems to cover the same problem: https://ghc.haskell.org/trac/ghc/ticket/11829

Wonderful! I can confirm[1] that adding the following to the cabal file fixes the problem:

if os(darwin) ld-options: -Wl,-keep_dwarf_unwind

Shouldn't GHC do this by default when linking on OS X?

Bas

[1] https://github.com/basvandijk/darwin-cxx-exception-bug/commit/9b48441606d2fe... _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs