On 2019/5/20 16:28, Nikolay Borisov wrote:
On 20.05.19 г. 11:24 ч., Honglei Wang wrote:
Hi Nikolay,
I don't think we can do the s390 analysis just use the x86_64 crash
utility directly. I'm not familiar with cross build, but seems this
linkage might help:
https://developer.ibm.com/linuxonpower/2017/07/06/analyzing-openpower-kernel-dump-information-laptop/
This is exactly which got me started into trying to understand what it
takes to analyse s390 on x86_64. . Hence I've referenced the function
which is supposed to verify that a particular combination of host and
target is supported. I'm now interested in understanding why s390 on
x86_64 is not supported.
Crossing arch always makes me nuts. I'd recommend to view s390 vmcores
in a s390 machine. But if you just want to do some investigation on this
topic, I think s390 guys can give more details. I suppose they've tried it?
Honglei
On 2019/5/20 15:18, Nikolay Borisov wrote:
Hello Dave,
I'd like to better understand why s390-on-x86_64 analysis is not
supported e.g. respective pair in get_current_configuration is missing?
Is it due to the endianness mismatch ? gdb does support setting the
endianness of a target? Or are there other problems?
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
