lkml.org 
[lkml]   [2005]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: status of kernel memory debugging?
Date
> UML is still too strange for valgrind, despite progress on both sides
> (valgrind accepting more strange things and UML becoming less
> strange).
>
> I tried grinding UML a month or so ago, and its use of clone was a
> sticking point.
>

I think I read your remark, yes. Thanks for the update; I hoped some strides
had been made in that direction since then. Personally, I know to little
about the topic to be of any use.

I guess the best option is then using slab caches per object type, so that I
can at least find obvious memory leaks.

On a sidenote, it'll be interesting to see what valgrind reports once (if?)
the kernel gets a good grinding.

Willem
-
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: 2005-07-30 23:16    [W:0.035 / U:0.724 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site