lkml.org 
[lkml]   [2006]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Tracking down leaking applications
Rahul Karnik wrote:

>
>The process killed has been either httpd or cronolog so far. For now,
>I have upgraded to FC4's 2.6.16-1_1069 and added some swap, where
>previously there was none.
>
>Is there a way to:
>- confirm that it is a userspace and not a kernel issue?
>- track down the application that is leaking memory?
>
>
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:
- the 'ps' utility, to see who eats the memory
- valgrind - an excellent tool for tracking down memory leaks (and other
bugs, too). Comes with Fedora, but check the Web for a newer version.

Regards,

Leo.

>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/
>
>
>

-
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-10 08:40    [W:0.041 / U:0.764 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site