This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17696] Systemtap fails to find kernel tracepoints when kernel is built in a separate directory from source tree
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 09 Jan 2015 17:24:49 +0000
- Subject: [Bug runtime/17696] Systemtap fails to find kernel tracepoints when kernel is built in a separate directory from source tree
- Auto-submitted: auto-generated
- References: <bug-17696-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17696
--- Comment #3 from Josh Stone <jistone at redhat dot com> ---
(In reply to Zhuo QL from comment #2)
> Thanks for your work, it works well with the debian system provided kernel!
And thank your for testing!
> But, it still does not work with my self-built kernel(built with a seperate
> KBUILD_OUTPUT).
>
> I read the lines around your commit and some logs, then found line 11132 of
> tapsets.cxx:
>
> const char* name = dwarf_formstring (dwarf_attr (cudie, DW_AT_comp_dir, &attr));
>
> Here we still get the dir to /lib/modules/${uname -r}/build under this
> situation.
Ah, I see. I think it would be better in this case if we avoid using the
DW_AT_comp_dir at all when it is equal to the known s.kernel_build_tree. I'll
attach a patch to this effect.
--
You are receiving this mail because:
You are the assignee for the bug.