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: "Frank Ch. Eigler" <fche at redhat 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: Fri, 19 Dec 2008 09:58:10 +0900 (JST)
- Subject: Re: Discussion at Linux Foundation Japan Symposium
- References: <20081219085519.041D.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20081219004423.GB24081@redhat.com>
> > > > Systemtap always requires kernel debuginfo to use. Unfortunately,
> > > > it is hard for users of some distributions to have debuginfo.
> > >
> > > Those distributions ought to be lobbied to improve this situation,
> > > since there are many non-systemtap uses of debugging data - such as
> > > debuggers, kernel- and user-space crash dump analysis tools.
> >
> > [...]
> > In enterprise usage, crash dump analysis is provided by vendor.
> > but tapset run on customer. [...]
>
> That is just one scenario. Another compelling use for debuginfo is a
> tool like oprofile.
Yes and No.
I agreed with Oprofile also need debuginfo.
However, enterprise customer doesn't use Oprofile too.
From enterprise customer view, that is consultant or vendor business.