• State Accepted Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 120 subscribers
  • Views 2287 views
  • Users 0 members are here
Options
Related
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

Streamline doesn't show Linux kernel source in code section

KJ Yang

Hi Streamline team,

I'm trying to use Streamline to analyze a userspace program and a driver in the Linux kernel which is used by the userspace one.

I managed to get a capture with some of the functions I added to the Linux kernel but when I double click on the function it doesn't show anything in the code section (just empty table). When I attached my userspace program it worked fine and I could see the source code in the code section.

While creating the capture, I attached a debug vmlinux file as mentioned in "streamline/gator/README.md" file.

$ file vmlinux
vmlinux: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=4a2c0d4f1853fda4b1b6f86f2f68c0fb437ac585, with debug_info, not stripped

I'm analyzing a system running on Raspberry Pi 3 B+ with a custom Linux image based on Buildroot. I'm adding below some screenshots for my capture.

Note that the function "cv_neon_read" is part of the code I added to the linux kernel but when I double click on it, it doesn't show in code

Is there something I need to do to enabled the kernel code to be visible in the code section?

Thanks,
KJ Yang

Parents
  • 0 Arm Employee Badge in reply to KJ Yang

    Hi KJ,

    Streamline tries to locate the path to your application's source by querying the DWARF debug information. If the path in the debug info is not accessible, you will need to provide a location for the source files using path substitution. Ronan has provided the link to the current version of the User Guide that shows how to do this.

Reply
  • 0 Arm Employee Badge in reply to KJ Yang

    Hi KJ,

    Streamline tries to locate the path to your application's source by querying the DWARF debug information. If the path in the debug info is not accessible, you will need to provide a location for the source files using path substitution. Ronan has provided the link to the current version of the User Guide that shows how to do this.

Children
No data