On Tue, 2007-03-06 at 21:43 -0500, Morten Welinder wrote: > Try running sparse under valgrind to see if there is some memory > corruption at an > earlier stage. Randy, maybe you'll just post the .i file as is (perhaps compressed with bzip2)? It looks like your post has generated lots of interest, but nobody can reproduce the problem. It's a much bigger waste of bandwidth to have others download the -mm kernel. If the file is too large for the list, please send it to me, and I'll put it online. Or put that file on pastebin.com or turboupload.com. If I can reproduce the bug, with or without valgrind, I'll reduce the file to the minimal required for the bug to be see. I did it before. If sparse crashes for you only, then you'll need to debug it on your system, and it doesn't matter how big the file is. What matters is the backtrace and other info from gdb. -- Regards, Pavel Roskin - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
