[erlang-bugs] SASL can't store events larger than 64k

[Nicolas Charpentier]

Hi,

This bug is already known in R11B-5 
(http://www.erlang.org/pipermail/erlang-patches/2007-August/000186.html) 
and still exist in R12B-5.
The main problem this bug is that after a 'large event' the whole log 
file is corrupted.

I propose you a patch, compatible with existing log files, which ensure 
that we don't log too large events.
In case of a 'too large' event, I just log {corrupted,Binary}. Binary is 
the beginning of the binary representation of the event.

With this patch, the log file isn't corrupted and we still can find (and 
debugg) which events are too long.


Regards,
---
Nicolas Charpentier
http://charpi.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log_mf_h.erl.patch
Type: text/x-patch
Size: 1915 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20081124/4ad83c38/attachment.bin>