Re: FastMM - Expected memory leaks
- From: "Pierre le Riche" <pleriche@xxxxxxxxxxx>
- Date: Sat, 27 Aug 2005 23:26:07 +0200
Hi Ulf,
> aCount the (optional) expected number of leaks. I have chosen to use
> aClassName as a String instead of TClass as I assume that a lot of the
I like this idea a lot.... definitely worth implementing.
> Chosing the first version would make it relatively easy to detect if a
> leaks is an expected leak. Just walk the stack at the time of the leak and
> check if the given address is a return address on it.
FastMM4 only stores stack traces in FullDebugMode (Storing stack traces is
slow and uses a lot of extra memory.) Both your suggestions seem to require
stack traces. The leak checking has to work in performance mode as well, or
it will be less useful than it is now.
Regards,
Pierre
.
- Follow-Ups:
- Re: FastMM - Expected memory leaks
- From: Ulf Axelsson
- Re: FastMM - Expected memory leaks
- References:
- FastMM - Expected memory leaks
- From: Ulf Axelsson
- FastMM - Expected memory leaks
- Prev by Date: FastMM - Expected memory leaks
- Next by Date: Re: Fastcode MM B&V 0.50
- Previous by thread: FastMM - Expected memory leaks
- Next by thread: Re: FastMM - Expected memory leaks
- Index(es):
Relevant Pages
|