aboutsummaryrefslogtreecommitdiffstats
path: root/lib/cosFileTransfer/test
diff options
context:
space:
mode:
authorRichard Carlsson <[email protected]>2013-10-16 23:11:40 +0200
committerRichard Carlsson <[email protected]>2013-10-16 23:30:16 +0200
commite84e886d75698ab6af585959fead3fa3c0ca0168 (patch)
tree806a42f5daf810a774d07f27ed0b92d31191f5d3 /lib/cosFileTransfer/test
parent73d1b4a1cc5ef1898b650fc74063ab28bc85bcbf (diff)
downloadotp-e84e886d75698ab6af585959fead3fa3c0ca0168.tar.gz
otp-e84e886d75698ab6af585959fead3fa3c0ca0168.tar.bz2
otp-e84e886d75698ab6af585959fead3fa3c0ca0168.zip
Don't try to add the log_mf_h handler in sasl unless configured to do so.
The functions add_error_logger_mf/1 and delete_error_logger_mf/1 in sasl.erl are designed to do nothing if the handler configuration as returned by get_error_logger_mf/0 is 'undefined'. However, that function returns a triple {undefined,undefined,undefined} when the error_logger_mf_* configurations have not been set. This makes SASL always try to add the log_mf_h handler on startup, passing 'undefined' for each of the Dir, MaxB and MaxF parameters. The gen_event callback function log_mf_h:init/1 will then crash with a function_clause error, causing the handler to be silently removed again. This patch fixes the problem by making get_error_logger_mf/0 return the single atom 'undefined' as it is expected to do.
Diffstat (limited to 'lib/cosFileTransfer/test')
0 files changed, 0 insertions, 0 deletions