Hello,
I'm still trying to fix the problem.
semantic error: failed to retrieve return value location for vfs_write
(/build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/fs/read_write.c):
identifier '$return' at read-write.stp:7:6
source: if ($return> 0) {
^
I'm pretty sure CONFIG_DEBUG_INFO is enabled, and in
/build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/build/tegra2_seaboard,
a binary file vmlinux is 57MB. It should contain the debug information.
(cr) zhengda@zdpc
/build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-k
ernel-9999/build/tegra2_seaboard $ ls -l vmlinux
-rwxr-xr-x 1 zhengda portage 59419805 Jul 22 20:55 vmlinux
How does systemtap use the debug information? When it compiles the
script, does it need to read the debug information from the kernel
image? or it needs to read the .obj files of the kernel?
Any ideas how to debug the problem?
Thanks,
Da