diff options
author | Jean-Sébastien Pédron <[email protected]> | 2018-02-06 13:59:22 +0100 |
---|---|---|
committer | Jean-Sébastien Pédron <[email protected]> | 2018-02-09 10:42:47 +0100 |
commit | a5eb5642b84c6843611f718cfd105557f8a7a406 (patch) | |
tree | ef57441cc5a62ee0541f197cf6b22090ac115684 /lib/tools/test/tools.spec | |
parent | 2e5063371ca21eeabd9c20462c16fac0ee147028 (diff) | |
download | otp-a5eb5642b84c6843611f718cfd105557f8a7a406.tar.gz otp-a5eb5642b84c6843611f718cfd105557f8a7a406.tar.bz2 otp-a5eb5642b84c6843611f718cfd105557f8a7a406.zip |
ssl: Add the unexpected message to #alert{}
... in handle_common_event(), instead of passing it to
handle_own_alert() after wrapping it in a tuple with `StateName` (i.e.
`{StateName, Msg}`).
The `StateName` is passed to handle_normal_shutdown() and to
alert_user(). The latter has a clause matching it against `connection`.
Unfortunately, when the argument was in fact `{StateName, Msg}`, another
clause was executed which dropped the `active` flag value and forced it
to `false`, even if the state was actually `connection`. It meant that
later in send_or_reply(), the alert was not propagated to the user, even
though it should (`active` set to `true` or `once`).
Now that handle_common_event() always passes the actual `StateName`, the
problem is fixed.
ERL-562
Diffstat (limited to 'lib/tools/test/tools.spec')
0 files changed, 0 insertions, 0 deletions