From: Keith Owens <kaos@ocs.com.au>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Chuck Ebbert" <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>,
"Linus Torvalds" <torvalds@osdl.org>, "Andi Kleen" <ak@suse.de>
Subject: Re: [patch] i386: show_registers(): try harder to print failing code
Date: Wed, 19 Jul 2006 15:33:41 +1000 [thread overview]
Message-ID: <13471.1153287221@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 19 Jul 2006 00:12:32 +0200." <9a8748490607181512t11e9970eu1a7aa1ad1644ec54@mail.gmail.com>
"Jesper Juhl" (on Wed, 19 Jul 2006 00:12:32 +0200) wrote:
>On 18/07/06, Chuck Ebbert <76306.1226@compuserve.com> 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 instruction at the EIP is bracketed, which makes it obvious if you
got any preceding instructions or not.
next prev parent reply other threads:[~2006-07-19 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 18:22 Chuck Ebbert
2006-07-18 22:12 ` Jesper Juhl
2006-07-19 5:33 ` Keith Owens [this message]
2006-07-19 0:25 Chuck Ebbert
2006-07-19 8:59 ` Jesper Juhl
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=13471.1153287221@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=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®