On 05/02/07 11:06, Dave Anderson wrote:
And adding a bunch of new LKCD files at this point in its life-time
is not all that appealing if it can be avoided.
I agree.
> It fixed a problem here where I head a crash dump from a
customer
> using LKCD that showed a totally wrong backtrace in crash but lcrash
> worked fine.
I'm curious to know more about the unwind bug and if there is another
approach that can be taken to resolve it. Unwinding on IA-64 has been
pretty solid in the past, so I'm curious to know what the underlying
problem is. I haven't worked with any 2.6 kernels (> 2.6.10) kernels
and LKCD. Bernhard, since you've already debugged this, can you think
of a way to enhance get_lkcd_regs() to catch the eip as an alternative
solution? In other words, why did it miss finding the eip in your
dump?
Troy