Re: Exception Misconceptions
On Dec 19, 4:51 pm, "io_x" <a...@b.c.invalid> wrote:
"tanix" <ta...@mongo.net> ha scritto nel
messaggionews:hgg839$ot7$1@news.eternal-september.org...
In article
<3eacbb7a-4318-4fed-b71c-f5da24cfa...@s20g2000yqd.googlegroups.com>, James
Kanze <james.ka...@gmail.com> wrote:
Wasting weeks on cleaning up the memory leaks?
I have wasted MONTHS on trying to catch all the subtle
memory leaks in a sophisticated async based program because
of some network availability issues make you maintain all
sorts of queues, depending on user interaction, causing such
headaches, that you can not even begin to imagine from the
standpoint of memory leaks.
do you know, exist wrapper for malloc, that at end of the
program check if there are "memory leak" and report the result
to the screen
If the program ends, it doesn't leak memory, and practically,
there's no way any tool can tell whether there is a leak or not.
(Well, they can tell that some things are definitively leaked.
If there are no pointers to the memory, for example, it has
leaked.) What the tools do is suggest possible leaks.
With regards to the first statement, of course: I've worked on a
fairly large number of applications which didn't leak. Some of
them, you may have used, without knowing it, since many of the
programs I've worked on aren't visible to the user---they do
things like routing your telephone call to the correct
destination. (And the proof that there isn't a leak: the
program has run over five years without running out of memory.)
so memory leak can not be one problem if one use these special
"malloc" functions (like i use always with all bell that
sound)
I'll say it again: there's no silver bullet. In the end, good
software engineering is the only solution. Thus, for example, I
prefer using garbage collection when I can, but it's a tool
which reduces my workload, not something which miraculously
elimninates all memory leaks (and some of the early Java
applications were noted for leaking, fast and furious).
--
James Kanze