This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: uprobe.ko is resident in memory.
- From: Mark Wielaard <mjw at redhat dot com>
- To: wenji dot huang at oracle dot com
- Cc: systemTAP <systemtap at sources dot redhat dot com>
- Date: Mon, 16 Mar 2009 12:11:51 +0100
- Subject: Re: uprobe.ko is resident in memory.
- References: <49BDED27.2020903@oracle.com>
Hi Wenji,
On Mon, 2009-03-16 at 14:09 +0800, Wenji Huang wrote:
> In user-space probing, the uprobe module will be
> resident in memory even the stap exists.
>
> [wjhuang@F10-32bits systemtap]$ /sbin/lsmod|grep uprobe
> [wjhuang@F10-32bits systemtap]$ sudo stap -e 'probe
> process("/home/wjhuang/Download/git-1.5.6/git").function("main"){}'
> WARNING: side-effect-free probe 'probe_1383': keyword at <input>:1:1
> source: probe
> process("/home/wjhuang/Download/git-1.5.6/git").function("main"){}
> ^
> ^C[wjhuang@F10-32bits systemtap]/sbin/lsmod|grep uprobe
> uprobes 24176 0
>
> Is this on purpose or some specific consideration?
I believe it is a bug caused by the way we build uprobes on the fly
resulting in several oddities when using uprobe based scripts. See also:
http://sourceware.org/bugzilla/show_bug.cgi?id=5163
http://sourceware.org/bugzilla/show_bug.cgi?id=6883
Cheers,
Mark