Display HLL C when debugging Linux kernel source with TRACE32
up vote
0
down vote
favorite
I am debugging with Linux kernel LTS4.4 (arm32, cortexa7).
I already built successfully the kernel image as well as vmlinux.
I am using Debugger Lauterbach and Trace32 tool.
And use below command to load vmlinux and kernel source
B:: data.load.Elf /home/compile-kernel/linux-4.4.138/vmlinux /PlusVM /STRIPPART 4 /PATH "/home/src-kernel"
The loading progress is successful, but I don't see any C code (HLL), only asm.
After that, I try to show symbol.list.source
. However, the table List is empty.
Could you guys support me on this ! Thanks.
jtag trace32
|
show 1 more comment
up vote
0
down vote
favorite
I am debugging with Linux kernel LTS4.4 (arm32, cortexa7).
I already built successfully the kernel image as well as vmlinux.
I am using Debugger Lauterbach and Trace32 tool.
And use below command to load vmlinux and kernel source
B:: data.load.Elf /home/compile-kernel/linux-4.4.138/vmlinux /PlusVM /STRIPPART 4 /PATH "/home/src-kernel"
The loading progress is successful, but I don't see any C code (HLL), only asm.
After that, I try to show symbol.list.source
. However, the table List is empty.
Could you guys support me on this ! Thanks.
jtag trace32
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am debugging with Linux kernel LTS4.4 (arm32, cortexa7).
I already built successfully the kernel image as well as vmlinux.
I am using Debugger Lauterbach and Trace32 tool.
And use below command to load vmlinux and kernel source
B:: data.load.Elf /home/compile-kernel/linux-4.4.138/vmlinux /PlusVM /STRIPPART 4 /PATH "/home/src-kernel"
The loading progress is successful, but I don't see any C code (HLL), only asm.
After that, I try to show symbol.list.source
. However, the table List is empty.
Could you guys support me on this ! Thanks.
jtag trace32
I am debugging with Linux kernel LTS4.4 (arm32, cortexa7).
I already built successfully the kernel image as well as vmlinux.
I am using Debugger Lauterbach and Trace32 tool.
And use below command to load vmlinux and kernel source
B:: data.load.Elf /home/compile-kernel/linux-4.4.138/vmlinux /PlusVM /STRIPPART 4 /PATH "/home/src-kernel"
The loading progress is successful, but I don't see any C code (HLL), only asm.
After that, I try to show symbol.list.source
. However, the table List is empty.
Could you guys support me on this ! Thanks.
jtag trace32
jtag trace32
asked Nov 11 at 8:13
Thảo Hoàng Minh
18815
18815
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19
|
show 1 more comment
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246929%2fdisplay-hll-c-when-debugging-linux-kernel-source-with-trace32%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you sure that you've build the kernel with debug information?
– Holger
Nov 11 at 19:02
Yes. To be able to do Linux aware debugging, the vmlinux file must be compiled with debug info enabled. Thus, need to ensure that CONFIG_DEBUG_INFO is enabled in the kernel configuration. Probably find this option under “Kernel hacking -> Compile the kernel with debug info” (in newer kernel versions under “Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info”). Make sure that CONFIG_DEBUG_INFO_REDUCED is not set (Reduce debugging information).
– Thảo Hoàng Minh
Nov 12 at 4:58
Well, if sYmbol.List.SOURCE is showing you an empty window, you are probably still missing required debug information in your vmlinux file. A suitable vmlinux file should be about 10 times bigger the raw image file. In you screenshot TRACE32 is still loading the file (there is the orange progress bar a the bottom) Have you waited long enough?
– Holger
Nov 14 at 12:49
Hi Holger, of course I have waited for the progress completed. I just took the picture randomly for example.
– Thảo Hoàng Minh
Nov 15 at 9:19
lauterbach.com/frames.html?manual.html
– Thảo Hoàng Minh
Nov 15 at 9:19