[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: lua_Alloc alternative recommendations?
- From: "Peter Pimley" <peter.pimley@...>
- Date: Wed, 13 Dec 2006 19:59:14 -0000
"avoid using free/realloc etc, which I assume is the cause of the
What I'd do first is to write a wrapper that just calls free/realloc,
but logs* each call and alerts* you if it fails. At least then you'd
know for sure that this is where the trouble lies, rather than assuming
(* How you do these will depend on your hardware of course)
The example function (http://www.lua.org/manual/5.1/manual.html#3.7)
could be modified pretty easily.
The thing is; if realloc IS failing then you're in trouble whichever way
you look at it. Are you sure it's not some other part of your program
leaking or fragmenting memory?
Information contained in this e-mail is intended for the use of the addressee only, and is confidential and may be the subject of Legal Professional Privilege. Any dissemination, distribution, copying or use of this communication without prior permission of the addressee is strictly prohibited.The views of the author may not necessarily constitute the views of Kuju Entertainment Ltd. Nothing in this email shall bind Kuju Entertainment Ltd in any contract or obligation.
The contents of an attachment to this e-mail may contain software viruses which could damage your own computer system. While Kuju Entertainment has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email