crash-utility-bounces@redhat.com wrote on 29.09.2006 17:38:53:

> ville.mattila@stonesoft.com wrote:
>  
>  
> Right -- unfortunately the recompilation of the exact same kernel may
> cause a shift in kernel text addresses, which throws off the line number
> information.  You might try just running "crash vmlinux.dbg vmcore" and
> see what happens.  If it doesn't complain about a mis-match, you should
> be OK.  But if there is a shift in the text addressing, then there's a good
> chance that it will propagate up into the static data addressing as well,
> and the mis-match ensues...

 Thanks for very good explanation.

 I tried vmlinux.dbg and got
WARNING: could not find MAGIC_START!
crash: ../smp-dbg/boot/vmlinux-2.6.15.7+smp and crashdump.2006-08-15-11-13-23 do not match!

 I should mention that I had to patch crash so that it can read all the symbols. I originally
 got symbol overflows. e.g crash gave output:
crash: symbol count overflow (__func__.1)
crash: symbol count overflow (__func__.2)
crash: symbol count overflow (__func__.3)
crash: symbol count overflow (__func__.0)


 To get "dis -l" to work, should I just compile the vmlinux "-g" and extract the debug
 info to .debug file e.g, Like RHEL 3.0 does?

 Thanks,

 - Ville