2010-01-27 04:55:51     how to debug corrupt program

Document created by Aaronwu Employee on Aug 20, 2013
Version 1Show Document
  • View in full screen mode

2010-01-27 04:55:51     how to debug corrupt program

david wang (CHINA)

Message: 85196   

 

Hi,

 

  I've a program running on bf527 board, but it sometimes corrupts. From the corrupt message, I could not see any useful info. Does any one give me any advise on how to debug such situation? Thanks!

 

 

 

Data access CPLB miss

- Used by the MMU to signal a CPLB miss on a data access.

Defered Exception context

CURRENT PROCESS:

COMM=webs PID=189

TEXT = 0x00400000-0x004869d4        DATA = 0x006009d4-0x007851cc

BSS = 0x007851cc-0x01a20000  USER-STACK = 0x01a3fee0

 

return address: [0x018df828]; contents of:

0x018df800:  e800  0000  3010  1006  e801  0000  6000  0538

0x018df810:  0010  5041  3209  0a08  63f8  0688  6018  5402

0x018df820:  0c00  1853  0000  3212 [9950] 0c00  1844  300a

0x018df830:  2005  3211  9950  0c00  183f  6409  6018  5401

 

SEQUENCER STATUS:               Not tainted

SEQSTAT: 00002026  IPEND: 0030  SYSCFG: 0006

  HWERRCAUSE: 0x0

  EXCAUSE   : 0x26

RETE: <0x00000000> /* Maybe null pointer? */

RETN: <0x01b08000> /* unknown address */

RETX: <0x018df828> [ /lib/libuClibc-0.9.29.so + 0x1f828 ]

RETS: <0x018dcef0> [ /lib/libuClibc-0.9.29.so + 0x1cef0 ]

PC  : <0x018df828> [ /lib/libuClibc-0.9.29.so + 0x1f828 ]

DCPLB_FAULT_ADDR: <0xcc33cc33> /* unknown address */

ICPLB_FAULT_ADDR: <0x018df828> [ /lib/libuClibc-0.9.29.so + 0x1f828 ]

 

PROCESSOR STATE:

R0 : 00000003    R1 : cc33cc32    R2 : cc33cc33    R3 : 00000001

R4 : 00000000    R5 : 00000008    R6 : 01bf9bd8    R7 : 0000000e

P0 : 00000011    P1 : ffffffff    P2 : cc33cc33    P3 : 01bf9bd8

P4 : 0000000b    P5 : 00470ff7    FP : 01a39590    SP : 01b07f24

LB0: 018def29    LT0: 018def26    LC0: 00000000

LB1: 018dcf7b    LT1: 018dcf7a    LC1: 00000000

B0 : 6a6b7332    L0 : 00000000    M0 : f6a01dc6    I0 : 018f58f0

B1 : d9fc6796    L1 : 00000000    M1 : 00000000    I1 : 018f591c

B2 : a379d2e6    L2 : 00000000    M2 : 01a3f6a8    I2 : 00000000

B3 : 5c1e71b2    L3 : 00000000    M3 : 01a3f6ac    I3 : 255d4cbb

A0.w: 00000000   A0.x: 00000000   A1.w: 00000000   A1.x: 00000000

USP : 01a39590  ASTAT: 02003004

 

Hardware Trace:

   0 Target : <0x00102b70> /* unknown address */

     Source : <0xffa0056c> /* unknown address */

   1 Target : <0xffa004b8> /* unknown address */

     Source : <0xffa00414> /* unknown address */

   2 Target : <0xffa005e4> /* unknown address */

     Source : <0x018df826> [ /lib/libuClibc-0.9.29.so + 0x1f826 ]

   3 Target : <0x018df812> [ /lib/libuClibc-0.9.29.so + 0x1f812 ]

     Source : <0x018df806> [ /lib/libuClibc-0.9.29.so + 0x1f806 ]

   4 Target : <0x018df7fc> [ /lib/libuClibc-0.9.29.so + 0x1f7fc ]

     Source : <0x018dceec> [ /lib/libuClibc-0.9.29.so + 0x1ceec ]

   5 Target : <0x018dced0> [ /lib/libuClibc-0.9.29.so + 0x1ced0 ]

     Source : <0x018dcd20> [ /lib/libuClibc-0.9.29.so + 0x1cd20 ]

   6 Target : <0x018dcd0c> [ /lib/libuClibc-0.9.29.so + 0x1cd0c ]

     Source : <0x018dcbc4> [ /lib/libuClibc-0.9.29.so + 0x1cbc4 ]

   7 Target : <0x018dcba2> [ /lib/libuClibc-0.9.29.so + 0x1cba2 ]

     Source : <0x018dce44> [ /lib/libuClibc-0.9.29.so + 0x1ce44 ]

   8 Target : <0x018dce3a> [ /lib/libuClibc-0.9.29.so + 0x1ce3a ]

     Source : <0x018dcb8e> [ /lib/libuClibc-0.9.29.so + 0x1cb8e ]

   9 Target : <0x018dcb84> [ /lib/libuClibc-0.9.29.so + 0x1cb84 ]

     Source : <0x018dd07a> [ /lib/libuClibc-0.9.29.so + 0x1d07a ]

  10 Target : <0x018dd074> [ /lib/libuClibc-0.9.29.so + 0x1d074 ]

     Source : <0x018dd062> [ /lib/libuClibc-0.9.29.so + 0x1d062 ]

  11 Target : <0x018dcfec> [ /lib/libuClibc-0.9.29.so + 0x1cfec ]

     Source : <0x018dcb80> [ /lib/libuClibc-0.9.29.so + 0x1cb80 ]

  12 Target : <0x018dcb7a> [ /lib/libuClibc-0.9.29.so + 0x1cb7a ]

     Source : <0x018dd2b8> [ /lib/libuClibc-0.9.29.so + 0x1d2b8 ]

  13 Target : <0x018dd2b2> [ /lib/libuClibc-0.9.29.so + 0x1d2b2 ]

     Source : <0x018dd42e> [ /lib/libuClibc-0.9.29.so + 0x1d42e ]

  14 Target : <0x018dd420> [ /lib/libuClibc-0.9.29.so + 0x1d420 ]

     Source : <0x018def2c> [ /lib/libuClibc-0.9.29.so + 0x1ef2c ]

  15 Target : <0x018def1e> [ /lib/libuClibc-0.9.29.so + 0x1ef1e ]

     Source : <0x018deeee> [ /lib/libuClibc-0.9.29.so + 0x1eeee ]

Stack from 01b07f04:

        ffa00a82 ffa00570 0027a614 0027a614 0027a610 01a397a4 00000009 018df868

        018df828 00000030 00002026 00000000 01b08000 018df828 018df828 018dcef0

        00000003 02003004 018dcf7b 018def29 018dcf7a 018def26 00000000 00000000

        00000000 00000000 00000000 00000000 5c1e71b2 a379d2e6 d9fc6796 6a6b7332

        00000000 00000000 00000000 00000000 01a3f6ac 01a3f6a8 00000000 f6a01dc6

        255d4cbb 00000000 018f591c 018f58f0 01a39590 01a39590 00470ff7 0000000b

 

Call Trace:

QuoteReplyEditDelete

 

 

2010-01-27 04:58:08     Re: how to debug corrupt program

david wang (CHINA)

Message: 85197   

 

Each time , the below registers are the same. I think this maybe a clue. But I don't know how to do.

 

R0 : 00000003    R1 : cc33cc32    R2 : cc33cc33    R3 : 00000001

QuoteReplyEditDelete

 

 

2010-01-27 05:04:31     Re: how to debug corrupt program

Mike Frysinger (UNITED STATES)

Message: 85198   

 

please read the documentation

 

  docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:analyzing_traces

QuoteReplyEditDelete

 

 

2010-01-27 10:31:45     Re: how to debug corrupt program

Robin Getz (UNITED STATES)

Message: 85208   

 

David:

 

What version of the dist are you using? Best thing to do might be to upgrade.

 

-Robin

Attachments

    Outcomes