Bart Van Assche wrote: >>The attached patch to valgrind-3.3.0 is what I am using to run >>UML (UserModeLinux) for x86 under memcheck on x86, thus checking >>the memory accesses of a linux kernel.
> This sounds great. Can you share your experience with running UML under > memcheck ? Details will appear in [EMAIL PROTECTED] and have started to appear in [EMAIL PROTECTED] . In general, running UML under memcheck is much the same as running any large application under memcheck for the first time. "Bugs" crawl out of the woodwork left and right. The kernel allocators make some assumptions that are unfriendly to memcheck. Threads are a serious nuisance. Debugging is tedious. printf and "for(;;);" are your friends (to avoid timing-dependent problems, and so you can attach gdb to a specific address space.) Getting a traceback of UML under memcheck is cumbersome. The best progress often is made by writing a program to detect and isolate the bug (editing the source of the kernel and/or memcheck, recompiling, and re-running) rather than by general external application of gdb. The *option* for memcheck to complain as soon as possible, immediately upon fetch of uninit bits, without waiting for array indexing or a conditional jump/move, is sorely missed. -- John Reiser, [EMAIL PROTECTED] ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
