From: Borislav Petkov <bp@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] scripts/decodecode: Decode 32-bit code correctly on x86_64
Date: Fri, 5 Mar 2021 23:19:51 +0100 [thread overview]
Message-ID: <20210305221951.GC2896@zn.tnic> (raw)
In-Reply-To: <20210305183948.37738-1-andriy.shevchenko@linux.intel.com>
On Fri, Mar 05, 2021 at 08:39:48PM +0200, Andy Shevchenko wrote:
> On x86_64 host the objdump uses current architecture which is 64-bit
> and hence decodecode shows wrong instructions.
>
> Fix it by supplying '-M i386' in case of ARCH i?86 or x86.
At the beginning of the script says:
# e.g., to decode an i386 oops on an x86_64 system, use:
# AFLAGS=--32 decodecode < 386.oops
What kind of oops are you decoding such that that doesn't work for you?
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2021-03-05 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 18:39 Andy Shevchenko
2021-03-05 22:19 ` Borislav Petkov [this message]
2021-03-08 9:59 ` Andy Shevchenko
2021-03-08 10:17 ` Borislav Petkov
2021-03-08 10:22 ` Andy Shevchenko
2021-03-08 11:12 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210305221951.GC2896@zn.tnic \
--to=bp@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome