This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Stap option to specify location of kernel binary
- From: Srikar Dronamraju <srikar at linux dot vnet dot ibm dot com>
- To: Roland McGrath <roland at redhat dot com>
- Cc: ananth at in dot ibm dot com, "Frank Ch. Eigler" <fche at redhat dot com>, systemtap at sources dot redhat dot com
- Date: Thu, 6 Mar 2008 12:53:52 +0530
- Subject: Re: Stap option to specify location of kernel binary
- References: <20050915143706.GC2612@redhat.com> <20050915215408.9D357180A19@magilla.sf.frob.com> <20080305161127.GA8945@in.ibm.com> <20080305214249.B822F27010F@magilla.localdomain>
- Reply-to: Srikar Dronamraju <srikar at linux dot vnet dot ibm dot com>
Hi Roland,
> > It would be good to be able to tell stap where to look for the kernel
> > binary, now that we now allow non-root 'stap'ing.
> >
> > It is quite possible that a non-root user running stap on a machine with
> > custom built kernel would want to use stap by specifying such an option.
> >
> > Thoughts?
>
> stap -r ~/mybuild
The release(-r) option in stap helps in building a tracing module(upto
pass 4) for a kernel version which is different from the currently
booted kernel.
It would be useful if user can specify the debuginfo file/path for the
currently running kernel. If non-root stap user has debuginfo
corresponding to the current kernel but does not have enuf permissions
to place the debuginfo file in specified paths then this feature would
be very useful.
There are two related issues here.
- debug vmlinux file may reside in other than the default search path of
systemtap.
- Filename may have a name other than vmlinux like vmdbg.
--
Thanks and Regards
Srikar