From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Ian McDonald" <imcdnzl@gmail.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Update to BUG-HUNTING
Date: Wed, 22 Feb 2006 20:39:46 -0800 [thread overview]
Message-ID: <20060222203946.f698d8ed.rdunlap@xenotime.net> (raw)
In-Reply-To: <cbec11ac0602221147n75e077cep9718c637f9761acd@mail.gmail.com>
On Thu, 23 Feb 2006 08:47:39 +1300 Ian McDonald wrote:
> Hi there,
Lo,
> +Finding bugs is not always easy. Have a go though. If you can't find it don't
> +give up. Report as much as you have found to the relevant maintainer. See
> +MAINTAINERS for who that is for the subsystem you have worked on.
or that you are having problems with.
> +To debug a kernel, use objdump and look for the hex offset from the crash
> +output to find the valid line of code/assembler. Without debug symbols, you
> +will see the assembler code for the routine shown, but if your kernel has
> +debug symbols the C code will also be available. (Debug symbols can be enabled
> +in the kernel hacking menu of the menu configuration.) For example:
> +
> + objdump -r -S -l --disassemble net/dccp/ipv4.o
> +
> +NB.: you need to be at the top level of the kernel tree for this to pick up
> +your C files.
> +
> +If you don't have access to the code you can also debug on some crash dumps
> +e.g. crash dump output as shown by Dave Miller.
> +
> +> EIP is at ip_queue_xmit+0x14/0x4c0
> +> ...
> +> Code: 44 24 04 e8 6f 05 00 00 e9 e8 fe ff ff 8d 76 00 8d bc 27 00 00
> +> 00 00 55 57 56 53 81 ec bc 00 00 00 8b ac 24 d0 00 00 00 8b 5d 08
> +> <8b> 83 3c 01 00 00 89 44 24 14 8b 45 28 85 c0 89 44 24 18 0f 85
> +>
> +> Put the bytes into a "foo.s" file like this:
> +>
> +> .text
> +> .globl foo
> +> foo:
> +> .byte .... /* bytes from Code: part of OOPS dump */
> +>
> +> Compile it with "gcc -c -o foo.o foo.s" then look at the output of
> +> "objdump --disassemble foo.o".
Maybe add this:
You can also take the "Code:" <object code> and feed it as bytes into a
.S (assembly) source file, assemble that, then objdump the .o file.
This is especially useful if the "Code:" line is one of the best clues
that you have. Andi Kleen has a script for doing this. It's called
'decodecode' and it's available from
ftp://ftp.firstfloor.org/pub/ak/shell/decodecode
---
~Randy
next prev parent reply other threads:[~2006-02-23 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 19:47 Ian McDonald
2006-02-23 4:39 ` Randy.Dunlap [this message]
[not found] ` <cbec11ac0602231509ke137da7ge0653bb50b20b62d@mail.gmail.com>
2006-02-24 4:21 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2005-12-20 2:25 Ian McDonald
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=20060222203946.f698d8ed.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=imcdnzl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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®