Broken gen:call/3?
Sean Hinde
sean.hinde@REDACTED
Mon Oct 31 13:55:31 CET 2005
Hi,
This behaviour seems broken to me:
1. One process is linked to another (for supervision reasons), and a
gen_*:call/2 synchronous request is made from one to the other.
2. The called process crashes while handling the call.
3. gen:call consumes *both* it's own monitor 'DOWN' message *and* the
'EXIT' message arising from the link
Result: calling process doesn't get 'EXIT' message, and hence doesn't
know about the crash. It does not then function well as a supervisor...
Sean
More information about the erlang-questions
mailing list