From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Andi Kleen" <ak@suse.de>, "Linus Torvalds" <torvalds@osdl.org>,
"Andrew Morton" <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: show_registers(): try harder to print failing code
Date: Tue, 18 Jul 2006 20:25:37 -0400 [thread overview]
Message-ID: <200607182027_MC3-1-C55F-B4E8@compuserve.com> (raw)
In-Reply-To: <9a8748490607181512t11e9970eu1a7aa1ad1644ec54@mail.gmail.com>
On Wed, 19 Jul 2006 00:12:32 +0200, Jesper Juhl wrote:
>
> > show_registers() tries to dump failing code starting 43 bytes
> > before the offending instruction, but this address can be bad,
> > for example in a device driver where the failing instruction is
> > less than 43 bytes from the start of the driver's code. When that
> > happens, try to dump code starting at the failing instruction
> > instead of printing no code at all.
> >
> Shouldn't the kernel be printing some info noting that this fallback
> is in use then? Or will that be completely obvious and I'm just not
> able to see that?
The code byte at EIP is marked with '<>', so it's obvious:
Code: <a1> 00 00 00 00 c7 04 24 05 30 b5 de 89 44 24 04 e8 f5 6f 5c e1 c9 31 c0 c3 00 00 00 00 00 00 00
--
Chuck
next reply other threads:[~2006-07-19 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 0:25 Chuck Ebbert [this message]
2006-07-19 8:59 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 18:22 Chuck Ebbert
2006-07-18 22:12 ` Jesper Juhl
2006-07-19 5:33 ` Keith Owens
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=200607182027_MC3-1-C55F-B4E8@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®