This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: register_kprobe undefined symbol on 2.6.11 of X86_64
Jim,
BTW, I found a definition in the original kernel 2.6.11 confused me a
little. Could you help me to figure it out?
in file include/asm-x86_64/kprobes.h
typedef u8 kprobe_opcode_t;
in file include/asm-sparc64/kprobes.h
typedef u32 kprobe_opcode_t;
I think this might be the problem why my OS is stuck since we are using
a u8 as kprobe_opcode_t. And I think regardless the architecture, the
size of the opcode of sparc64 and x86_64 should be same?
Thanks,
Neo
On Wed, 2005-07-06 at 16:23 -0500, Neo Jia wrote:
> Jim,
>
> Thanks. It seems your way solve such "unknown symbol" problem. But the
> system is stuck when I insert the module, this is the reason why I send
> you response a little bit late, reboot twice. : )
>
> Currently, I am monitoring the do_fork function. Is it too sensitive to
> be monitored? When I get rid of the function address of the kp,
> everything is OK.
>
> BTW, how can I remove that module? rmmod cannot work?
>
> Thanks,
> Neo
>
>
> On Wed, 2005-07-06 at 14:00 -0700, Jim Keniston wrote:
> > On Wed, 2005-07-06 at 13:23, Neo Jia wrote:
> > > Ananth,
> > >
> > > Not i386, I am working on the arch as x86_64 SMP, this is the reason why
> > > I have to try 2.6.11 not 2.6.9.
> > >
> > > Yes, the KPROBES is enabled in the .config.
> > >
> > > And, I even find the register_kprobe in the Module.symvers file.
> > >
> > > I attached the .c file I just wrote FYI in this attachment.
> > >
> > > Thanks,
> > > Neo
> >
> > Have you tried adding this line to the end of your .c file?
> >
> > MODULE_LICENSE("GPL");
> >
> > I don't have an x86_64 system immediately available, but that made a
> > difference on my i386 system.
> >
> > Jim Keniston
--
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!