Many people (myself included) have wished that Valgrind could run UML properly. But what problems, exactly, should valgrind be able to detect?
For instance, it would be unreasonable to expect valgrinding UML to be able to find memory leaks in programs running under UML. (Don't laugh, somebody asked that very thing of valgrind and wine.) Naively, I would expect valgrinding UML to be able to find wild pointer references, references to freed memory, and real uses of uninitialized variables inside kernel code. But I'm not completely sure that I know enough to define those terms more concretely. (Perhaps kernel memory allocation is complicated enough that it's not simple to define them.) It would probably be useful to put together an example kernel module that made a bunch of mistakes that might reasonably be detected by valgrind. I'll probably do that sometime soon, but thought I'd bring up the idea in case anybody else had thought about it already. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
