From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BUG() disassembly tweak
Date: Sat, 11 May 2002 12:21:55 +1000 [thread overview]
Message-ID: <3622.1021083715@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 11 May 2002 03:07:51 +0100." <Pine.LNX.4.21.0205110258480.2235-100000@localhost.localdomain>
On Sat, 11 May 2002 03:07:51 +0100 (BST),
Hugh Dickins <hugh@veritas.com> wrote:
>On Sat, 11 May 2002, Keith Owens wrote:
>>
>> IMNSHO the instructions _after_ the oops are almost useless.
>
>Oh, I agree: I'd be perfectly happy for ksymoops to abandon trying
>to disassemble the instructions after the oops, and I don't think
>it need try to disassemble the instructions before the oops either.
>
>It is important that it show the bytes (preferably before and)
>after the oops, so that an investigator can locate that sequence
>of bytes in a built object; and it is important that we have some
>tool (objdump) which can disassemble the built object despite ud2
>and its accompanying data; but ksymoops does not need to do it.
ksymoops does more than decode the instructions. It does all the work
required to build the dummy object ready for objdump to do the
decoding. It also massages the objdump output to make it more readable
and does symbol lookup on the absolute addresses returned by objdump.
next prev parent reply other threads:[~2002-05-11 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 21:22 Hugh Dickins
2002-05-10 22:10 ` Linus Torvalds
2002-05-10 22:51 ` Dave Jones
2002-05-11 11:42 ` Ingo Oeser
2002-05-10 22:58 ` Andrew Morton
2002-05-11 0:00 ` Keith Owens
2002-05-11 1:58 ` Hugh Dickins
2002-05-11 2:32 ` Kai Germaschewski
2002-05-11 3:03 ` Keith Owens
2002-05-11 1:04 ` Hugh Dickins
2002-05-11 1:34 ` Keith Owens
2002-05-11 1:39 ` Keith Owens
2002-05-11 2:07 ` Hugh Dickins
2002-05-11 2:21 ` Keith Owens [this message]
2002-05-13 15:31 ` Hugh Dickins
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=3622.1021083715@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®