Yedidyah Bar-David wrote:
> efence only causes buffer overruns to segv, nothing more.
>
> Eli - If you only looked at a leak detector - don't look at efence.
Thanks.
Just to CTBS: It's true that I was looking only for mem leaks detector;
However, during my tries to use njadm (New Just Anothe
Hetz Ben Hamo wrote:
> You may want to contact rational,
>
> from what I know, they DO have some sort of beta test but they want some
> customers before they'll release it to market - that what I heard from
> someone there 2 months ago.
I had a feeling like this...
In the ads of IBM about the
> On Thu, Nov 22, 2001, Yedidyah Bar-David wrote about "Re: Mem Leak Tracer (monitored
>malloc)":
> > Hi
> >
> > I never used any of them, so I can't comment.
> >
> > For my needs, ElectricFence is good enough. It is tiny, I understand
> &
Hetz Ben Hamo <[EMAIL PROTECTED]> writes:
> Oh, and insure sucks, specially when it finds tons of other leaks,
> but not in your code, in the other libs code ;)
I didn't see that all that much, and when it happened it was simple
to make it shut up about the particular things.
One thing about In
Hi
On Thu, Nov 22, 2001 at 09:47:19PM +0200, Nadav Har'El wrote:
> On Thu, Nov 22, 2001, Yedidyah Bar-David wrote about "Re: Mem Leak Tracer (monitored
>malloc)":
> > Hi
> >
[snip]
>
> I thought the original poster was after a memory *leak*
On Thu, Nov 22, 2001, Hetz Ben Hamo wrote about "Re: Mem Leak Tracer (monitored
malloc)":
> Oh, and insure sucks, specially when it finds tons of other leaks, but not in
> your code, in the other libs code ;)
So what? If it tells you these leaks occur because of memory allo
On Thu, Nov 22, 2001, Omer Musaev wrote about "RE: Mem Leak Tracer (monitored malloc)":
> bugs in hellish efficiency. However, there is a catch.
>
> It is for WinNT( ++ ) or Solaris on SPARC only. period.
I remember using it on a VAX running Unix!
I guess Purify changed t
On Thu, Nov 22, 2001, Eli Marmor wrote about "Re: Mem Leak Tracer (monitored malloc)":
> I was not aware of memprof...
> Seems that my search in freshmeat, although it brought zillion results,
> was not full anough...
> I'll take a look at it!
If you're
On Thu, Nov 22, 2001, Yedidyah Bar-David wrote about "Re: Mem Leak Tracer (monitored
malloc)":
> Hi
>
> I never used any of them, so I can't comment.
>
> For my needs, ElectricFence is good enough. It is tiny, I understand
> perfectly how it works, and what
You may want to contact rational,
from what I know, they DO have some sort of beta test but they want some
customers before they'll release it to market - that what I heard from
someone there 2 months ago.
Oh, and insure sucks, specially when it finds tons of other leaks, but not in
your code
i have tried a lot of malloc debuggers and i can recommend dmalloc it's very
good for finding leaks and validate pointers , but if you want simple and
clear reporting try using memprof ( you can find it on freshmeat) it has a
very good gtk gui for reporting leaks and profiling , but unfortunal
Hi
I never used any of them, so I can't comment.
For my needs, ElectricFence is good enough. It is tiny, I understand
perfectly how it works, and what I can expect from it. Most others
are much bigger. The extreme is checker (package gccchecker in debian),
which puts some checks inside all memor
Eli Marmor <[EMAIL PROTECTED]> writes:
> Does anybody have any experience with one or more of them?
> Any recommendations?
I have used dmalloc and ElectricFence. Both are very helpful.
> Tips?
In the past I found it very useful to compile with ParaSoft's Insure
during development. It flushes a
Hi,
We all love the plurality of choices in Linux/Open-Source.
However, it doesn't come without a price: The difficulty to choose a
package from so many "competing" packages.
I used freshmeat to search for a memory leak tracer.
In return, I got an infinite list of libraries, all claim to do wh
> Looks good, but if I decide to buy a product, I believe I'll put my
> money on Purify.
Purify is the best tool I had worked with. It works well on multithreaded
apps.
It does not touch your code ( opposing to Insure++ ). It is reliable and
points to
bugs in hellish efficiency. However, there
Thanks a lot, Shlomi/Yedidya/Vlad/Oleg (though others are still welcome
to contribute from their experience too...)
Mid-Summary:
Yedidyah Bar-David wrote:
> I never used any of them, so I can't comment.
>
> For my needs, ElectricFence is good enough. It is tiny, I understand
As I w
16 matches
Mail list logo
