Re: [Crash-utility] CA SEOS module causes heartburn for crash(1)
"Kurtis D. Rader" wrote:
I was asked to look at a s390 SUSE dump which had the Computer
Associates
SEOS product modules loaded (seos and ksymadd). They exported symbols
with addresses well below the address space for modules. For example,
"dynamic_Seos_syscall_num" with an address of 0x4f90dc0 which is well
below the base of the first module at 0x7880d000. This results in crash
trying to mmap an anonymous 1.9 GB region. Which naturally fails on a
s390 system where the address space is only 2 GiB in size.
Anyone else run across this? Should crash be able to deal with this or
should I simply tell the customer to stop using CA's SEOS product if they
want us to look at their crash dumps?
Hi Kurt,
I'm deferring this to the IBM guys who deal with s390, SUSE kernels, and
whatever dumpfile format this is (LKCD or s390 native?).
But I'm curious -- where in the crash utliity is an mmap being done?
Dave
--
Kurtis D. Rader, Level 3 Linux Support
ABC Service Center, Linux Change Team
T/L 775-3714, DID +1 503-578-3714
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility