Logging of "quality events"
jseward at acm.org
Thu Sep 19 08:12:50 UTC 2013
On 09/19/2013 04:50 AM, Nicholas Nethercote wrote:
> This makes me think of
Having grappled with low level event logging in both the above bug and
in Valgrind (the -d option), I'd say it's remarkably difficult to
construct something which is guaranteed deadlock-free if you want it
to be usable in marginal situations, for example when jemalloc is not
initialised or is compromised (though heap corruption).
In both cases I inclined strongly to making the logger as self-contained
as possible, even to the point of either avoiding dynamic memory
allocation, or having its own private allocator. Relying on layers of
other libraries in such cases tends to be a fast-track to deadlocks
and/or segfaults, IME.
More information about the firefox-dev