[RFC][PATCH 0/4][kprobe](djprobe) Direct jump optimized kprobes
Ingo Molnar
mingo@redhat.com
Tue Nov 28 16:34:00 GMT 2006
On Tue, 2006-11-28 at 23:40 +0900, Masami Hiramatsu wrote:
> > If existing in-kernel debug info is not enough then i'd suggest to
> add
> > an extra build pass to the kernel to add it (dependent on
> > CONFIG_KPROBES) - a'la CONFIG_UNWIND_INFO. Am i missing something?
>
> As far as I know, there is no debuginfo in the kernel which is
> loaded in the memory. But the debuginfo is included in the
> "vmlinux" file (not the "vmlinuz" file).
correct, that sort of debug info is not included in the kernel image -
but some of it could be included - just like unwind info, or kallsyms
and other info is included currently. Whatever can be extracted at build
time we can also insert into the kernel image. The info that is needed
here is a table of all valid instruction boundaries, correct?
OTOH, userspace (SystemTap) has all this information handy already,
because it already has to parse the -g debuginfo - hence it's more
natural to delegate this there?
Ingo
More information about the Systemtap
mailing list