This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Discussion at Linux Foundation Japan Symposium
- From: KOSAKI Motohiro <kosaki dot motohiro at jp dot fujitsu dot com>
- To: "Jun Koi" <junkoi2004 at gmail dot com>
- Cc: kosaki dot motohiro at jp dot fujitsu dot com, "Satoshi OSHIMA" <satoshi dot oshima dot fk at hitachi dot com>, systemtap at sourceware dot org, <mhiramat at redhat dot com>, <hisashi dot hashimoto dot wh at hitachi dot com>, "Yumiko SUGITA" <yumiko dot sugita dot yf at hitachi dot com>
- Date: Thu, 18 Dec 2008 18:27:32 +0900 (JST)
- Subject: Re: Discussion at Linux Foundation Japan Symposium
- References: <494A053D.4030808@hitachi.com> <fdaac4d50812180057q35b2303djc12dc06ff470bec2@mail.gmail.com>
> > (3) Make no debuginfo version
> >
> > Systemtap always requires kernel debuginfo to use.
> > Unfortunately, it is hard for users of some distributions
> > to have debuginfo.
> >
>
> How is it possible to do that without kernel debug info? Currently
> systemtap extracts lots of information on kernel layout from debug
> info, so I dont understand why we can survive without that.
At least, dtrace don't need debuginfo.
On Solaris 10, kernel and all executable binary have own tracing purpose
information in special elf section.
it can't be stripped and gurantee exist although product application binary.
http://blogs.sun.com/ali/entry/what_is_sunw_ldynsym
Of cource, this approach indicate systemtap lost some feature.
(e.g. above section don't have line number information and local
variable name information)
but it is still useful for average tracing user.