Holger Weiß
2015-04-09 19:47:16 UTC
The gen_tcp:controlling_process/2 and inet_sctp:connect/[45] functions
may (indirectly) call prim_inet:setopt/3. Up to Erlang/OTP R16x, errors
returned by those prim_inet:setopt/3 calls were ignored. Since 17.0, a
badmatch exception is generated if prim_inet:setopt/3 doesn't return ok.
This commit propagates the error to the caller, instead:
git fetch git://github.com/weiss/otp.git propagate-setopt-error
Links:
https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error
https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error.patch
https://github.com/erlang/otp/pull/674
may (indirectly) call prim_inet:setopt/3. Up to Erlang/OTP R16x, errors
returned by those prim_inet:setopt/3 calls were ignored. Since 17.0, a
badmatch exception is generated if prim_inet:setopt/3 doesn't return ok.
This commit propagates the error to the caller, instead:
git fetch git://github.com/weiss/otp.git propagate-setopt-error
Links:
https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error
https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error.patch
https://github.com/erlang/otp/pull/674