lkml.org 
[lkml]   [2006]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Tracking down leaking applications
On 4/10/06, Leonid Kalev <lion@odcnet.com> wrote:
> This seems a bit off-topic for LKML, because you should *always* check
> user-space for memory leaks before blaming the kernel. A few things that
> can help you with your questions:

Not blaming the kernel yet, just wondering if it can help me track
down the offending app.

> - the 'ps' utility, to see who eats the memory

Well, httpd is at the top of the list, as it should be. What I cannot
tell is if the processes are leaking memory, or if all is well.

> - valgrind - an excellent tool for tracking down memory leaks (and other
> bugs, too). Comes with Fedora, but check the Web for a newer version.

I will try valgrind on the web application.

Thanks for the help!

-Rahul
--
Rahul Karnik
rahul@genebrew.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-13 16:15    [W:0.056 / U:1.848 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site