From: Chris Vaill <chris@FanClubIndustries.com>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I'd like a bit of help on tracing my oops
Date: 12 Nov 2001 18:17:29 -0500 [thread overview]
Message-ID: <1005607056.1226.5.camel@toronja> (raw)
In-Reply-To: <3BF047EF.883A1D@nortelnetworks.com>
In-Reply-To: <3BF047EF.883A1D@nortelnetworks.com>
On Mon, 2001-11-12 at 17:06, Christopher Friesen wrote:
>
> At this point I'm not entirely certain how to track down the exact line of code
> where it's dying. If I am reading it right, then the program counter was at
> 90016720, is this correct? Then disassembling vmlinux in gdb should give me the
> instruction corresponding to that address, at which point I need to correlate
> that to the actual code to figure out what's happening, correct? Is it expected
> that disassembling vmlinux will give the same code as doing a make <file.s> in
> the linux tree?
What I like to do is to add -g to CFLAGS in Makefile. Then you can do
an "objdump -S vmlinux" and see the original source interspersed with
the disassembled code.
Chris
prev parent reply other threads:[~2001-11-12 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 22:06 I'd like a bit of help on tracing my oops Christopher Friesen
2001-11-12 23:17 ` Chris Vaill [this message]
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=1005607056.1226.5.camel@toronja \
--to=chris@fanclubindustries.com \
--cc=cfriesen@nortelnetworks.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