[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: identifying cause of segfault with gdb?
|
From: |
Paul Pluzhnikov |
|
Subject: |
Re: identifying cause of segfault with gdb? |
|
Date: |
15 Jul 2004 23:20:03 -0700 |
|
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) |
Vijay Patil <vijaypatil78@yahoo.com> writes:
> Is there any way to find memory leaks using GDB?
No.
> Regards,
> Vijay
>
> --- Guy Harrison <swamp-DEL-dog@ntlworld.com> wrote:
Please do not top-post.
Please do not ask unrelated question in a follow-up to someone else's message.
Please start a new thread instead.
Finally, to find memory leaks (and many other bugs) on Linux/x86, use valgrind.
Many other free: ccmalloc, dmalloc, mpatrol, and commercial: Purify,
Insure++ tools are available on other platforms.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.