start_link and death of parent

[Fredrik Linder]

Hello OTP Folks

I get this very strange behaviour from otp-r9c-0 built on redhat-8 or redhat-9 (not 100% sure which).

Is this a known problem in r9c-0, and if so is it corrected in r9c-1?

(traffic@REDACTED)265> whereis(d).
undefined
(traffic@REDACTED)266> l(d).
{module,d}
(traffic@REDACTED)267> P=spawn(fun()->io:format("result: ~w~n", [catch d:start_link()]) end).
<1308.2281.0>
result: {ok,<1308.2282.0>}
(traffic@REDACTED)268> erlang:is_process_alive(P).
false
(traffic@REDACTED)269> whereis(d).
<1308.2282.0>
(traffic@REDACTED)270> erlang:is_process_alive(whereis(d)).
true
(traffic@REDACTED)271> exit(whereis(d),kill).
true
(traffic@REDACTED)272> whereis(d).
undefined
(traffic@REDACTED)273>

Shouldn't <1308.2282.0> die when <1308.2281.0> dies.

The 'd' module is just the emacs skeleton for gen_server in of r9c-0 with -define(SERVER, ?MODULE).

/Fredrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: d.erl
Type: application/octet-stream
Size: 4689 bytes
Desc: d.erl
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20040617/14384023/attachment.obj>