Re: [Crash-utility] crash-7.3.2 very long list iteration progressively increasing memory usage
On 06/28/2018 11:09 PM, David Wysochanski wrote:
One problem with all of these non-storage location algorithms is
that
it won't give you the precise location of the start of the loop in the
list (i.e. the one with the corrupted 'prev' list entry.
I am not sure if this is a show stopper but that is fairly important
information in most instances.
Um, one list-walker checking the back-pointer against where it
just came from would seem to suffice for that?
--
Jeremy