• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 562 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Kernel debug: not able to let program stop at breakpoint

Eason Wang
Genius 13460 points


Hi expert,

I am not able to let program stop at breakpoint.

I checked with the tutorial I had, and find there is one difference in the screenshot:

I followed this link to debug CCS:

http://processors.wiki.ti.com/index.php?title=Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5#Perform_Linux_Kernel_Debug

The screenshot shows the breakpoints can be seen both in debug and breakpoint window, 

but from my side itcan not be seen in the debug window

I just doubt it is a sign that something is not properly set. Could you give some advice?

BR,

Eason

  • 0
    TI__Genius 13460 points

    I feel like the vmlinux was not successfully generated with debug infomation.   the size is around 8M. I am workng on DM8148

    But all I did was follow the tutorial and I have double checked the .config that the menuconfig options has been enabled.

  • 0 in reply to Eason Wang
    TI__Intellectual 2625 points

    Hi Eason,

    vmlinux symbols should be in 0xC0000000- ranges (depending how it was built).

    It looks like the cpu halted at the address space of a user program (0x80000000- range).

    Since the debugger does not have symbols about the user program, that is why no call stack is generated.

    Try setting a breakpoint at some linux kernel function, for example, schedule (which is called whenever the OS switches tasks).

    Regards,

    Raymond