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
Hi Lei
Good to hear you are trying out the Linux Kernel Debug support in Arm Development Studio.
The warning is given because the breakpoint is being set before the debug symbols for that code have been loaded. So the debugger sets a "pending" breakpoint for you, expecting the debug symbols to be loaded later, and helpfully warns you what it is doing.
Have you loaded the debug symbols for the kernel from the vmlinux file?If so, are you sure the debug symbols for vlan.c are actually present in the vmlinux file, or are they in a different shared module?Does code execution stop correctly at the breakpoint?
You might find this blog usefulcommunity.arm.com/.../debugging-the-armv8-a-linux-kernel-with-ds-5
This was written for DS-5 (the forerunner of Arm DS), but most of the flow is similar.
Hope this helps to get you (re)started!
Stephen
Thanks for your reply. I used the win 10 to install the Arm Development studio.
I used the existing source code to create project. The path to source code include upper letter and lower letter, after I modify it to use only lower letter, the issue was gone. I am not sure whether the issue only happen in windows or my PC.
Hi LeiThanks 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