Francesco Biscani

heyoka 4.0.3 contains a tentative fix for this issue, I will be closing the report. Please re-open if needed.

@yurivict the test is complaining that a generic ``std::exception`` is thrown instead of the more specific ``std::bad_function_call`` (which does inherit from ``std::exception``): https://en.cppreference.com/w/cpp/utility/functional/bad_function_call I don't understand how this is possible,...

> This code catches `std::bad_function_call` as thrown on FreeBSD: > > ``` > #include > #include > > int main() { > try { > throw std::bad_function_call(); > } catch...

@yurivict would you mind checking if the attached patch makes any difference? https://gist.github.com/bluescarni/67b13d5959535ae2f58754741b1f8a73

Ok, thanks for checking. Under the assumption that FreeBSD is using libc++ as its C++ standard library... (otherwise, disregard everything I am writing here). I noticed there is a difference...

@yurivict sorry disregard the above post, it turns out I was not looking at the correct file... ``bad_function_call`` does have the correct attribute set, at least on my local copy......

@yurivict see also this report: https://github.com/llvm/llvm-project/issues/54863#issuecomment-1096977132

@yurivict could you tell me if the libc++ version you are using contains the symbol for ``std::bad_function_call``? I.e., does something like ```bash $ readelf -s -C --wide /usr/lib/libc++.so.1.0 |grep -i...

@yurivict would you mind checking also if ``libheyoka.so`` contains the symbol for ``bad_function_call``? I.e., something like ```bash $ readelf -s -C --wide libheyoka.so|grep -i bad_func ``` executed from the ``build``...

@yurivict are you still experiencing this issue on recent heyoka versions?