• State Accepted Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 120 subscribers
  • Views 27866 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No compilation unit matching "path_to/linux_kernel/net/8021q/vlan.c" was found

lei wang

Hi,

We installed a new ARM Development studio. And use it to debug the linux kernel. I followed "About debugging a Linux kernel" and "Configuring a connection to a Linux kernel" chapters to debug.

I can connect to CPU and stop it, step one instruction each time, but I can not set breakpoint. I got following messages when I set breakpoint

WARNING(CMD452-COR167):
! Breakpoint 11 has been pended
! No compilation unit matching "path_to/linux_kernel/net/8021q/vlan.c" was found

 

Our target board was based on i.MX8qxp, the debugger is DSTREAM-ST

Parents
  • 0 Arm Employee Badge in reply to lei wang

    Hi Lei

    Thanks for letting us know that you resolved the problem.

    Problems with the case of filenames are common (and expected) when using Linux kernel on Windows. This are due to Windows not being able to differentiate between upper and lower case in filenames (e.g. foo.h versus foo.H), where Linux treats these as separate files.

    Stephen

Reply
  • 0 Arm Employee Badge in reply to lei wang

    Hi Lei

    Thanks for letting us know that you resolved the problem.

    Problems with the case of filenames are common (and expected) when using Linux kernel on Windows. This are due to Windows not being able to differentiate between upper and lower case in filenames (e.g. foo.h versus foo.H), where Linux treats these as separate files.

    Stephen

Children
No data