Re: sh: inconsistent kallsyms data

Quoting Paul Mundt <lethal@xxxxxxxxxxxx>:

> On Fri, Dec 31, 2004 at 05:59:31PM +0000, pmarques@xxxxxxxxxxxx wrote:
> > I think the only change from 2.6.9 that could affect this is the
> > addition of the is_arm_mapping_symbol from Russel King.
> > 
> This wouldn't make any difference as that only gets invoked by
> read_symbol() for U type symbols, which is unrelated.


You mis-read the 'if'. The symbol is not used it is of 'U' type *or*
is_arm_mapping_symbol. This means that is_arm_mapping_symbol will be called for
all the symbols that are not of type 'U'.

Anyway, Keith Owens might be right. I forgot that this change only went into the
official tree now, and was under the impression that was already in 2.6.9 :(

It seems from the symptoms that the kallsyms_names array was 0x70 bytes larger
on the second run. This shouldn't happen if the algorithm is ran over the same
symbols, not matter how complex the algorithm is.

I was the one who wrote the algorithm, so I'm probably in the best position to
debug it. If you send Keith the info he requested, send it to me too, so that I
have some more data to look at.

--
Paulo Marques - www.grupopie.com

"A journey of a thousand miles begins with a single step."
Lao-tzu, The Way of Lao-tzu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/