The GSL’s airy_Ai function gsl_sf_airy_Ai_e  triggers a floating-point division-by-zero exception with the input -1.842761151977744. The exception can be trapped by using “feenableexcept”, but it will disappear if you slightly disturb the input, say, to -1.84276115198. By digging into the issue, I have observed that in the airy_mod_phase function that airy_Ai invokes, the variable result_m is divided whereas it has vanished following a non-trivial computation (with loops, etc., in function cheb_eval_mode_e). Please check the code airy_divbyzero.c below.