[Crash-utility] README: Reword crash support for arch different than host arch

[Santosh Yadawar]

“The crash binary can only be used on systems of the same architecture as
the host build system.”
This statement on first read made me think that crash running on particular arch can handle vmcore of that arch only.

Thanks, Santosh

---------- Forwarded message ---------
From: Dave Anderson <anderson at redhat.com<mailto:anderson at redhat.com>>
Date: Fri, Dec 6, 2019 at 12:04 PM
Subject: Re: [Crash-utility] README: Reword crash support for arch different than host arch
To: Discussion list for crash utility usage, maintenance and development <crash-utility at redhat.com<mailto:crash-utility at redhat.com>>


The point is that regardless whether the target vmcore is from
a different architecture, the "alternate" crash binary that is
built with "make target=XXX" must match the architecture of the
host.

Dave

----- Original Message -----
>
>
> Hi,
>
>
>
>
>
> May be this rewording is needed?
>
>
>
>
>
>
>
> crash$ git diff README
>
> diff --git a/README b/README
>
> index 62855c2..3bef5ec 100644
>
> --- a/README
>
> +++ b/README
>
> @@ -82,9 +82,10 @@
>
> must be configured and built. Alternatively, the crash source RPM file
>
> may be installed and built, and the resultant crash binary RPM file
> installed.
>
>
>
> - The crash binary can only be used on systems of the same architecture as
>
> - the host build system. There are a few optional manners of building the
>
> - crash binary:
>
> + The crash binary built as above can only be used on systems of the same
>
> + architecture as the host build system. However crash can be built to handle
>
> + dumpfiles from different architecture than host build system, here are the
>
> + available build options:
>
>
>
> o On an x86_64 host, a 32-bit x86 binary that can be used to analyze
>
> 32-bit x86 dumpfiles may be built by typing "make target=X86".
>
>
>
>
>
>
>
>
>
> Thanks,
>
> Santosh
>
> --
> Crash-utility mailing list
> Crash-utility at redhat.com<mailto:Crash-utility at redhat.com>
> https://www.redhat.com/mailman/listinfo/crash-utility<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fcrash-utility&data=02%7C01%7Csayadawa%40microsoft.com%7Cd6f7a19438244fbac5f308d77c6853b0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637114659830185241&sdata=AwKSEQeTjESbK6%2FTjHI%2BlDXXWet7c5FBAprivK%2FJyow%3D&reserved=0>

--
Crash-utility mailing list
Crash-utility at redhat.com<mailto:Crash-utility at redhat.com>
https://www.redhat.com/mailman/listinfo/crash-utility<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fcrash-utility&data=02%7C01%7Csayadawa%40microsoft.com%7Cd6f7a19438244fbac5f308d77c6853b0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637114659830185241&sdata=AwKSEQeTjESbK6%2FTjHI%2BlDXXWet7c5FBAprivK%2FJyow%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20191209/0665e010/attachment.htm>