[erlang-questions] Why does this not work in the latest otp
Thomas James Malone
If I use the module I have included as an attachement and run the
following code in R13B01,
db_dis:new(database, remote@macbook).
db_dis:write(tom, london, database, remote@macbook).
db_dis:write(stuart, london, database, remote@macbook).
db_dis:match(tom, database, remote@macbook).
=ERROR REPORT==== 24-Jun-2009::15:13:11 ===
'local@macbook' got a corrupted external term from 'remote@macbook' on
distribution channel 5571
<<...,106>>
ATOM_CACHE_REF translations: 0='local@macbook', 1=''
timeout
In R12B-5 if run the same code I get my expected response of []
what am I missing.
thanks in advance
Tom
Raimo Niskanen
the new atom cache code!
Simply when sending [] (the empty list) as the _complete_
message to a remote process, decoding fails in R13B01.
That is serious and it is interesting to note that
sending [] as the complete message between remote
processes must be _very_ uncommon, oddly enough.
You are the only one so far that has encountered it.
The developer that wrote the new atom cache (now on vacation)
has given me a two-line patch to regression test. First shot
on one platform works fine and I do not expect any problems.
Next week I will post the patch if the regression tests run fine.
>
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
--
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org
Raimo Niskanen
> Congratulations, you have found a serious bug in
> the new atom cache code!
>
> Simply when sending [] (the empty list) as the _complete_
> message to a remote process, decoding fails in R13B01.
> That is serious and it is interesting to note that
> sending [] as the complete message between remote
> processes must be _very_ uncommon, oddly enough.
> You are the only one so far that has encountered it.
>
> The developer that wrote the new atom cache (now on vacation)
> has given me a two-line patch to regression test. First shot
> on one platform works fine and I do not expect any problems.
> Next week I will post the patch if the regression tests run fine.
Sorry about the delay.
I had almost totally unrelated problems in the regression tests.
(caused by the same developer, otherwise totally unrelated).
But here is the two-line patch (attached). It works fine
in our regression tests (when they run).