Hello,
* Dave Anderson <anderson(a)redhat.com> [2006-12-08 19:37]:
I wish I could help you out, but w/respect to anything associated
with
LKCD, I'm only a receptor of patches from the LKCD developers on the
list, and I personally don't do any work with them at all.
That whole ia64-specific lkcd_fix_mem.c file came from Troy Heber for
ia64 LKCD dumpfile support (troy.heber(a)hp.com). Troy's an active
contributor on this list, and may have a quick answer -- I'm afraid I
have no idea what it does...
Anyway, thanks for the information!
Yes I agree (presuming that eventually the list turns into 64-bit
symbol values). But I don't see any attachment other than your pgp
signature?
Sorry, I just forgot it. Here it is.
And yes, the values are larger in the end. And also our
/boot/System.map on IA64 has zero-prefixes. The map.4 file is
generated by lkcd, and they simply don't use the zero prefixes. Which
should not matter, IMO. So I vote for applying the attached patch.
I'd never seen those types of __crc_ absolutes, probably because
they don't show up in our kernels. The closest 2.6.5-era ia64
Red Hat kernel (2.6.5-1.358) System.map starts out like this:
a00000010010c5a0 T I_BDEV
a0000001005bd140 r __ksymtab_I_BDEV
a0000001005c6ca8 r __kstrtab_I_BDEV
a00000010030ff60 T QUIRK_LIST
a0000001005c0950 r __ksymtab_QUIRK_LIST
a0000001005cb698 r __kstrtab_QUIRK_LIST
a000000100714ff8 S ROOT_DEV
a0000001005bb020 r __ksymtab_ROOT_DEV
a0000001005c4248 r __kstrtab_ROOT_DEV
a00000010030fd00 T SELECT_DRIVE
a0000001005c0920 r __ksymtab_SELECT_DRIVE
a0000001005cb660 r __kstrtab_SELECT_DRIVE
a00000010030fde0 T SELECT_INTERRUPT
Whatever... maybe a different build CONFIG or something?
Hm ..., I also don't understand why the /boot/System.map of the same
kernel isn't identical to the map.4 file generated by klcd. In fact,
map.4 is missing symbol and gdb fails to load. But even with the
/boot/System.map of the right kernel, it doesn't work (i.e. backtrace
is complete garbage).
But first I'll fix the header format which _is_ different in crash and
our SLES9 kernel (and klcdutils), and if it then doesn't work I'll
come back to the system maps.
Thanks for your help!
Regards,
Bernhard