• 30、应用调试之配置内核输出应用程序的段错误信息


    应用程序在执行的时候,如果驱动程序出现问题,会打印oops或者堆栈分析信息,也是是从在内核态下会打印错信息,而如果应用程序本身有问题,其执行时在用户态,只会提示段错误信息,这时候需要修改内核,让其支持应用出错时打印更多信息,根据oops信息搜索“”“Unable to handle kernel  ”,查看内核打印这些信息的代码(在arch/arm下搜索会快些),发现在arch/arm/mm/fault.c的__do_kernel_fault函数中被执行,该文件中也有do_user_fault,查看该函数,发现如果定义了CONFIG_DEBUG_USER,且user_debug变量被设置了,当应用程序出问题时(即在用户态下)就会有打印信息

    arch/arm/mm/fault.c

    __do_user_fault(struct task_struct *tsk, unsigned long addr,
      unsigned int fsr, unsigned int sig, int code,
      struct pt_regs *regs)
    {
    struct siginfo si;

    #ifdef CONFIG_DEBUG_USER // 1. 配置内核(在make menuconfig之后查找DEBUG_USER)

    //在内核源代码的基础上新增代码处,可以打印回溯栈

    unsigned long ret;

    unsigned long val;

    int i=0;


    if (user_debug & UDBG_SEGV) {
    printk(KERN_DEBUG "%s: unhandled page fault (%d) at 0x%08lx, code 0x%03x ",
    tsk->comm, sig, addr, fsr);
    show_pte(tsk->mm, addr);
    show_regs(regs);

    //在内核源代码的基础上新增代码处,可以打印回溯栈

    printk("Stack: ");

    while(i<1024)

    {

    if(copy_from_user(&val,(const void __user *)(regs->ARM_sp + i*4),4))

      break;

    printk("%08x ",val);

    i++;

    if(i%8==0)

      printk(" ");

    }

    printk(" End of Stack");
    }
    #endif

    2. uboot: set bootargs user_debug=0xff

    set bootargs console=ttySAC0 root=/dev/nfs nfsroot=192.168.1.123:/work/nfs_root/first_fs ip=192.168.1.17 ipaddr=192.168.1.17 user_debug=0xff

    3. 执行APP
    ./test_debug
    a = 0x12
    pgd = c04c8000
    [00000000] *pgd=33d08031, *pte=00000000, *ppte=00000000

    Pid: 772, comm: test_debug
    CPU: 0 Not tainted (2.6.22.6 #1)
    PC is at 0x84ac
    LR is at 0x84d0
    pc : [<000084ac>] lr : [<000084d0>] psr: 60000010
    sp : bed9fe40 ip : bed9fe54 fp : bed9fe50
    r10: 4013365c r9 : 00000000 r8 : 00008514
    r7 : 00000001 r6 : 000085cc r5 : 00008568 r4 : bed9fec4
    r3 : 00000012 r2 : 00000000 r1 : 00001000 r0 : 00000000
    Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
    Control: c000717f Table: 304c8000 DAC: 00000015
    [<c002cd1c>] (show_regs+0x0/0x4c) from [<c0031a98>] (__do_user_fault+0x5c/0xa4)
    r4:c04a6840
    [<c0031a3c>] (__do_user_fault+0x0/0xa4) from [<c0031d38>] (do_page_fault+0x1dc/0x20c)
    r7:c00261e0 r6:c0024cf8 r5:c04a6840 r4:ffffffec
    [<c0031b5c>] (do_page_fault+0x0/0x20c) from [<c002b224>] (do_DataAbort+0x3c/0xa0)
    [<c002b1e8>] (do_DataAbort+0x0/0xa0) from [<c002be48>] (ret_from_exception+0x0/0x10)
    Exception stack(0xc3e7bfb0 to 0xc3e7bff8)
    bfa0: 00000000 00001000 00000000 00000012
    bfc0: bed9fec4 00008568 000085cc 00000001 00008514 00000000 4013365c bed9fe50
    bfe0: bed9fe54 bed9fe40 000084d0 000084ac 60000010 ffffffff
    r8:00008514 r7:00000001 r6:000085cc r5:00008568 r4:c039bfc8
    Segmentation fault

    Stack: (修改do_user_fault后出现以下栈信息,最开始是出错位置的函数栈)
    00000000 becd3e64 becd3e54 000084d0 000084a0 00000000 becd3e78 becd3e68
    C's sp             return addr      B's sp

    000084f0 000084c4 00000000 becd3e98 becd3e7c 00008554 000084e4 00000000
    ret addr        A's sp              ret addr     main's sp

    00000012 becd3ec4 00000001 00000000 becd3e9c 40034f14 00008524 00000000
                            ret addr        caller's sp
    对于动态链接,已经退出的程序不好确定动态库的地址(可以通过gdb的方式确认,在gdb中输入info file命令,可以看出应用程序中各段地址是什么库或者函数,但是视频中还是没分析出来,下面会采用静态链接的方式,静态链接的时候所以相关文件都会在反汇编中找到)

    00000000 0000839c 00000000 00000000 4001d594 000083c4 000085cc 4000c02c
    becd3ec4 becd3f7b 00000000 becd3f88 becd3f92 becd3f99 becd3fad becd3fb8
    becd3fdb becd3fe9 00000000 00000010 00000003 00000006 00001000 00000011
    00000064 00000003 00008034 00000004 00000020 00000005 00000006 00000007
    40000000 00000008 00000000 00000009 0000839c 0000000b 00000000 0000000c
    00000000 0000000d 00000000 0000000e 00000000 00000017 00000000 0000000f
    becd3f77 00000000 00000000 00000000 00000000 76000000 2e006c34 7365742f
    65645f74 00677562 52455355 6f6f723d 4f480074 2f3d454d 61706900 3d726464
    2e323931 2e383631 37312e31 52455400 74763d4d 00323031 48544150 62732f3d
    2f3a6e69 2f727375 6e696273 69622f3a 752f3a6e 622f7273 53006e69 4c4c4548
    69622f3d 68732f6e 44575000 2e002f3d 7365742f 65645f74 00677562 00000000

    4. 反汇编app:
    arm-linux-objdump -D test_debug > test_debug.dis

    在 test_debug.dis中查找84ac :str r3,[r2]  //把r3寄存器里面的值存在r2地址处

    对于静态链接的test_debug(上面是动态链接的方式,main函数被动态链接库调用,但不好分析栈找到调用者在哪里,这里采用静态链接的方式在确认main函数被那个调用,然后继续分析),编译应用程序的时候加上-static
    PC is at 0x81e0
    LR is at 0x8204
    pc : [<000081e0>] lr : [<00008204>] psr: 60000010
    sp : be93dc60 ip : be93dc74 fp : be93dc70
    r10: 000085f4 r9 : 00008248 r8 : be93deb4
    r7 : 00000001 r6 : 00000000 r5 : be93dd3e r4 : 00000000
    r3 : 00000012 r2 : 00000000 r1 : 00001000 r0 : 00000000
    Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user

    Stack:
    00000000 be93dc84 be93dc74 00008204 000081d4 00000000 be93dc98 be93dc88
    C'sp              ret addr        B'sp

    00008224 000081f8 00000000 be93dcb8 be93dc9c 00008288 00008218 00000000
    ret addr       A'sp              ret addr        main'sp

    00000012 be93deb4 00000001 00000000 be93dcbc 000084ac 00008258 756e694c
                            ret addr        __libc_start_main'sp

    00000078 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 32393100
    3836312e 312e312e 00000037 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 2e320000
    32322e36 0000362e 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 23000000
    54203335 4d206575 31207961 31322035 3a34303a 43203834 32205453 00323130
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    766d7261 006c7434 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    6f6e2800 0029656e 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 000080f8 00008680 00000000 be93deb4 be93df6a 00000000 be93df77
    be93df81 be93df92 be93df99 be93dfad be93dfb8 be93dfdb be93dfe9 00000000
    00000010 00000003 00000006 00001000 00000011 00000064 00000003 00008034
    00000004 00000020 00000005 00000003 00000007 00000000 00000008 00000000
    00000009 000080d0 0000000b 00000000 0000000c 00000000 0000000d 00000000
    0000000e 00000000 00000017 00000000 0000000f be93df66 00000000 00000000
    00000000 34760000 2f2e006c 74736574 6265645f 55006775 3d524553 746f6f72
    444c4f00 3d445750 6f72702f 34372f63 4f480033 2f3d454d 61706900 3d726464
    2e323931 2e383631 37312e31 52455400 74763d4d 00323031 48544150 62732f3d
    2f3a6e69 2f727375 6e696273 69622f3a 752f3a6e 622f7273 53006e69 4c4c4548
    69622f3d 68732f6e 44575000 2e002f3d 7365742f 65645f74 00677562 00000000

  • 相关阅读:
    张拥军:解码商品期货投资实战应用 2011年06月02日
    罗小奔:谈一下最近商品期货套利的几个机会
    罗小奔:商品期货套利当前之我见
    leetcode -- Binary Tree Preorder Traversal
    leetcode -- Linked List Cycle II
    leetcode -- Linked List Cycle
    [转载]2014年10月26完美世界校招两道java题
    [转载]SQL truncate 、delete与drop区别
    [转载]会引起全表扫描的几种SQL
    [转载]Linux I/O 调度方法
  • 原文地址:https://www.cnblogs.com/liusiluandzhangkun/p/8681882.html
Copyright © 2020-2023  润新知