[Crash-utility] backtrace failure on x86_64 and x86 in 2.6.33/34 kernels due to "thread_return" removal

Dave Anderson anderson at redhat.com
Fri May 21 12:50:00 UTC 2010


----- "Masami Hiramatsu" <mhiramat at redhat.com> wrote:

> Hi Dave,
> 
> Are these issues only for crash tools? or it occurs in kernel func-backtrace too?
> And how would you fix it?

They are crash issues only, in having to deal with the shifting sands of
the underlying kernel.  

In both cases, the problem has always been that assembly-code labels are
stored as text symbols, which is confusing to the backtrace code.  And in
both cases, the new kernel changes interfered with the work-arounds put in
place by the crash utility to handle them.

In any case, it's not a big deal as it's fixable in the crash utility.

Thanks,
  Dave





More information about the Crash-utility mailing list