On Tue, 9 Aug 2005, Peter Hagervall wrote:
>
> Yes, assuming c8b9ce8f1ef27a0e77c87ea1581c6e2b33753e7a is the current
> HEAD. My arch is x86.
Yup, that's what I tested too.
> The straightforward way of using it is just prepending the command line
> with 'valgrind', so in this case I have:
I just get "missing --tool option" from that.
I did a "valgrind --tool=memcheck" thing, and yes, I see two invalid reads
in clean_up_insns too.
I suspect that valgrind could find better errors if it was told about
"allocate()" and "free_one_entry()". As it is, it won't notice any normal
allocation mis-use, because it just sees them as one mmap. The
clean_up_insns one seems to be from some of the (rare) malloc/free users,
namely the ptr_list allocations.
The fact that the pointer list that is warned about was free'd by
"simplify_switch()" is interesting - that sure as hell is some very
special code. And valgrind did _not_ complain about kernel/sched.c, for
example, so it's certainly not a normal error.
> I'll try to track down the problem later tonight.
Thanks. I'll see if I get around to looking closer later too.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
