Matthew Lye wrote:
> If I understand correctly, the leak reporting relies on whether or not
> there's a pointer to the memory block, or some such thing. It also
> relies on the use (ultimately) of the system's standard malloc, I
> think. The documentation is a bit above my comprehension lev
On 2-Dec-07, at 12:03 PM, Christian Biere wrote:
> Isn't there a counter which shows how often this leak occurs? If
> there's only
> one, there's probably some initialization the first time one of
> these functions
> is called and it's not really a leak. If this happens for each
> handshake,
Matthew Lye wrote:
> The following also seems to be a source of several memory leaks, about
> 144 bytes each. I'd found 1k-sized leaks earlier, but unfortunately
> the "Instruments" program crashed before they could be recorded. I
> believe they involved a call to TLS as well, though, so th
The following also seems to be a source of several memory leaks, about
144 bytes each. I'd found 1k-sized leaks earlier, but unfortunately
the "Instruments" program crashed before they could be recorded. I
believe they involved a call to TLS as well, though, so they could
have been from t
