Re: Exception Misconceptions
On Dec 21, 9:16 am, ta...@mongo.net (tanix) wrote:
In article <4b2f3095$0$1110$4fafb...@reader3.news.tin.it>,
"io_x" <a...@b.c.invalid> wrote:
"James Kanze" <james.ka...@gmail.com> ha scritto nel messaggio
news:4f3858fa-d8e2-4c92-970f-ae4d6d9913cc@s31g2000yqs.googlegroups.com...
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, flip some bits in Visual Studio IDE and you'll get a
dump of ALL your memory leaks when the program terminates.
Except that from what little I've seen of it, it reports a lot
of things as leaks that aren't, and missing some important
leaks.
--
James Kanze