public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: BURJAN Gabor <burjang@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17-rc1 kernel panic at boot
Date: Tue, 18 Dec 2001 15:18:47 +1100	[thread overview]
Message-ID: <2375.1008649127@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 17 Dec 2001 09:29:05 -0800." <3C1E2B61.3F9A685E@zip.com.au>

On Mon, 17 Dec 2001 09:29:05 -0800, 
Andrew Morton <akpm@zip.com.au> wrote:
>BURJAN Gabor wrote:
>> >>NIP; c0264050 <vortex_probe1+394/cbc>   <=====
>> Trace; c0263f28 <vortex_probe1+26c/cbc>
>
>That's a big function, unfortunately.   Could you please
>do the following?
>
>In the top-level makefile, add the line:
>
>CFLAGS += -g
>
>right at the end.    Then rebuild the kernel, recreate the
>crash, then run:
>
>gdb vmlinux
>(gdb) l *0xc0264050

Not need to go quite that far.  It is not necessary to recompile the
entire kernel nor do you need to boot a kernel to get the source code
for an instruction.

cd linux
rm drivers/net/3c59x.o
make CFLAGS_3c59x.o=-g vmlinux
s=$(sed -ne '/vortex_probe1/s/ .*//p' System.map | tr '[a-z]' '[A-Z]')
e=$(echo -e "obase=16\nibase=16\n$s+500" | bc)
objdump -S --start-address=0x$s --stop-address=0x$e vmlinux

That recompiles just 3c59x.o with -g and dumps the first 0x500 bytes of
vortex_probe1, including the source code.


  reply	other threads:[~2001-12-18  4:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 12:08 2.4.17-rc1 kernel panic at boot BURJAN Gabor
2001-12-17 17:29 ` Andrew Morton
2001-12-18  4:18   ` Keith Owens [this message]
2001-12-18 14:23     ` BURJAN Gabor
2001-12-18 19:24       ` Andrew Morton
2001-12-19 13:29         ` BURJAN Gabor

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=2375.1008649127@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=akpm@zip.com.au \
    --cc=burjang@elte.hu \
    --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