Get backtrace information manually

[gan_xiao_jun@yahoo.com]

Hi
I think backbrace information reading from coredump
use gdb -c is very useful.

But Sometime in embeded system, it can't be read but
give following information:
../../gdb/regcache.c:552: internal-error:
set_register_cached: Assertion `regnum <
current_regcache->descr->nr_raw_registers' failed. A
problem internal to GDB has been detected, further
debugging may prove unreliable. Quit this debugging
session? (y or n)

So I can't located crash reason use gdb.

fortunately, tips are introduced to locate it
manually.

I can read /proc/kmsg to get  pc=0x00033148 from
following:
<7>myapp: unhandled page fault at pc=0x00033148,
lr=0x00033270 (bad address=0x00000000, code -1)
<4>pc : [<00033148>]    lr : [<00033270>]    Tainted:
P
<4>sp : bffff22c  ip : bffff2c0  fp : bffff2bc
<4>r10: 406137b8  r9 : 00000003  r8 : 00309df8
<4>r7 : 0031d320  r6 : bffff370  r5 : 0031d320  r4 :
bffff370 <4>r3 : 001e7a9c  r2 : 00000000  r1 :
0031e448  r0 : 00000000
<4>Flags: nZCv  IRQs on  FIQs on  Mode USER_32 
Segment user
<4>Control: 397F  Table: AC3B0000  DAC: 00000015
Then use nm to locate the function name and address
crash happens.
And use addr2line to locate the source file if it is
debug version.

But I am not sure is there a way to get backtrace
information manually.
Does anyone have tips about this?

Thanks for any comment
gan



		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail