public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* Mapping IIP value to Kernel Symbols
@ 2006-12-01 14:12 Karthik Gopalakrishnan
  2006-12-01 18:38 ` Yu, Fenghua
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Karthik Gopalakrishnan @ 2006-12-01 14:12 UTC (permalink / raw)
  To: linux-ia64

Hi All.

    I have a value of IIP that I recovered from an MCA. I want to
figure out which instruction in the Kernel resulted in the MCA. Please
let me know how I can find this information. I don't have a 'Kernel
Dump'. I am using the kernel that shipped with RHEL Release 4 Update
2. Since I wanted a relocatable kernel, I gunzip'ed the kernel. The
kernel didn't load at the default address.

    I am not familiar with the Kernel Debugging tools on Linux. I will
be grateful if you can provide suitable pointers.

Thanks & Regards,
Karthik

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Mapping IIP value to Kernel Symbols
  2006-12-01 14:12 Mapping IIP value to Kernel Symbols Karthik Gopalakrishnan
@ 2006-12-01 18:38 ` Yu, Fenghua
  2006-12-03  5:19 ` Karthik Gopalakrishnan
  2006-12-04 23:17 ` Peter Chubb
  2 siblings, 0 replies; 4+ messages in thread
From: Yu, Fenghua @ 2006-12-01 18:38 UTC (permalink / raw)
  To: linux-ia64

>    I have a value of IIP that I recovered from an MCA. I want to
>figure out which instruction in the Kernel resulted in the MCA. Please
>let me know how I can find this information. 

You can disassemble kernel to find the instruction for the IIP. The
command is "objdump -d kernel_name". You might also find its system.map
(under /boot) useful.

Thanks.

-Fenghua

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mapping IIP value to Kernel Symbols
  2006-12-01 14:12 Mapping IIP value to Kernel Symbols Karthik Gopalakrishnan
  2006-12-01 18:38 ` Yu, Fenghua
@ 2006-12-03  5:19 ` Karthik Gopalakrishnan
  2006-12-04 23:17 ` Peter Chubb
  2 siblings, 0 replies; 4+ messages in thread
From: Karthik Gopalakrishnan @ 2006-12-03  5:19 UTC (permalink / raw)
  To: linux-ia64

Hi Fenghua.

	Thank You very much. This is exactly what I was looking for. :-)

Regards,
Karthik

Yu, Fenghua wrote:
>>    I have a value of IIP that I recovered from an MCA. I want to
>> figure out which instruction in the Kernel resulted in the MCA. Please
>> let me know how I can find this information. 
> 
> You can disassemble kernel to find the instruction for the IIP. The
> command is "objdump -d kernel_name". You might also find its system.map
> (under /boot) useful.
> 
> Thanks.
> 
> -Fenghua
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mapping IIP value to Kernel Symbols
  2006-12-01 14:12 Mapping IIP value to Kernel Symbols Karthik Gopalakrishnan
  2006-12-01 18:38 ` Yu, Fenghua
  2006-12-03  5:19 ` Karthik Gopalakrishnan
@ 2006-12-04 23:17 ` Peter Chubb
  2 siblings, 0 replies; 4+ messages in thread
From: Peter Chubb @ 2006-12-04 23:17 UTC (permalink / raw)
  To: linux-ia64

>>>>> "Karthik" = Karthik Gopalakrishnan <karthik.g.krishnan@gmail.com> writes:

Karthik> Hi All.  I have a value of IIP that I recovered from an
Karthik> MCA. I want to figure out which instruction in the Kernel
Karthik> resulted in the MCA. 

I find the simplest way is usually to use gdb.

 gdb vmlinux
 gdb> x/i 0xaddress

You can also do
 gdb> list *0xaddress
to find the line iff the kernel was compiled with debugging info and
you have the source available.

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-12-04 23:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-01 14:12 Mapping IIP value to Kernel Symbols Karthik Gopalakrishnan
2006-12-01 18:38 ` Yu, Fenghua
2006-12-03  5:19 ` Karthik Gopalakrishnan
2006-12-04 23:17 ` Peter Chubb

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox