[erlang-bugs] Bug in the resolver?

Evgeniy Khramtsov <>
Fri Apr 15 13:34:33 CEST 2011


15.04.2011 18:01, Raimo Niskanen wrote:
> Hi.
>
> I now have reworked the code. It of course passes our regression tests,
> but since I have not yet managed to reproduce your bug it would be
> nice if you could test it. I pushed a branch rn/inet_res-crash-rest-time-0
> to my github repository git://github.com/RaimoNiskanen/otp.git from
> where it can be fetched. The branch has two commits to inet_res.erl.
>
>    http://github.com/RaimoNiskanen/otp/tree/rn/inet_res-crash-rest-time-0
>    * Check return values from UDP send functions
>      http://github.com/RaimoNiskanen/otp/commit/24f13b771e84b4baad3fb804e14e85478432e289
>    * Cleanup timeout handling, fix bug for remaining time =:= 0
>      http://github.com/RaimoNiskanen/otp/commit/684c8ea15059093d25d9c97c21bf1db091579f08
>
> If it is awkward for you to build from source, and you run R14B02
> I have placed the VM executable at http://erlang.org/~raimo/inet_res.beam
> that you can drop into your erlang installation. Be sure to keep
> the old around just in case I messed something up...
>
> Please report your test results...

Thank you very much. I'm trying your beam (I have R14B02 installed). By 
the way, the problem is rare, so it can take a day to catch the error on 
heavily loaded machines. I'll report the result.

-- 
Regards,
Evgeniy Khramtsov, ProcessOne.
xmpp:



More information about the erlang-bugs mailing list