public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	        Satoshi OSHIMA <satoshi.oshima.fk@hitachi.com>,
	        systemtap@sourceware.org, mhiramat@redhat.com,
	        hisashi.hashimoto.wh@hitachi.com,
	        Yumiko SUGITA <yumiko.sugita.yf@hitachi.com>
Subject: Re: Discussion at Linux Foundation Japan Symposium
Date: Fri, 19 Dec 2008 23:51:00 -0000	[thread overview]
Message-ID: <494BFBBF.3090804@redhat.com> (raw)
In-Reply-To: <20081219004423.GB24081@redhat.com>

Frank Ch. Eigler wrote:
> Hi -
> 
> On Fri, Dec 19, 2008 at 08:58:58AM +0900, KOSAKI Motohiro wrote:
>>>> 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.
> 
> - FChE

For the case where oprofile data is being mapped back to lines in the source 
code debuginfo is needed. However, for the case just want to know which 
functions the code is spending time in oprofile doesn't use debugging 
information produced by -g; it just looks for the function locations in the 
code.  Unfortunately, the strip operations used for binaries in distribution 
strip out all information from the binary leaving just the minimal executable 
bits, making the debuginfo the only place to get that information.

It would be nice if there was something between the extremes of a huge amount of 
information in the debuginfo or nothing at all.


-Will

  parent reply	other threads:[~2008-12-19 19:54 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  8:33 Satoshi OSHIMA
2008-12-18  8:59 ` KOSAKI Motohiro
2008-12-18  9:07 ` Jun Koi
2008-12-18  9:21   ` jidong xiao
2008-12-18  9:28     ` Jun Koi
2008-12-18  9:35   ` KOSAKI Motohiro
2008-12-18  9:37     ` Jun Koi
2008-12-18  9:42       ` Jun Koi
2008-12-18  9:46         ` KOSAKI Motohiro
2008-12-18  9:58     ` K.Prasad
2008-12-18 10:02       ` KOSAKI Motohiro
2008-12-18 10:21         ` K.Prasad
2008-12-18 15:52         ` Masami Hiramatsu
2008-12-18 15:41 ` Masami Hiramatsu
2008-12-18 17:11 ` Frank Ch. Eigler
2008-12-19  0:08   ` KOSAKI Motohiro
2008-12-19  0:58     ` Frank Ch. Eigler
2008-12-19  1:39       ` KOSAKI Motohiro
2008-12-19 23:51       ` William Cohen [this message]
2008-12-20  1:51         ` Richard J Moore
2008-12-20 14:27         ` Masami Hiramatsu
2008-12-19  0:45   ` Masami Hiramatsu
2008-12-22 18:22 Frank Ch. Eigler
2008-12-22 20:38 ` Theodore Tso
2008-12-22 22:41   ` Frank Ch. Eigler
2008-12-23  0:33     ` Theodore Tso
2008-12-23  0:34       ` Masami Hiramatsu
2008-12-23  0:44         ` Theodore Tso
2008-12-23 21:13           ` Roland McGrath
2008-12-23 22:13           ` Masami Hiramatsu
2008-12-23 14:28       ` Frank Ch. Eigler
2008-12-23 22:21     ` Roland McGrath
2008-12-23 22:33       ` Masami Hiramatsu
2008-12-23 22:44         ` Roland McGrath
2008-12-24  3:40           ` Masami Hiramatsu
2008-12-24  8:48             ` Roland McGrath
2008-12-24 18:14               ` Masami Hiramatsu
2008-12-24 19:26                 ` Roland McGrath
2008-12-24 21:02                 ` Theodore Tso
2008-12-26 18:17                   ` Roland McGrath
2008-12-23 23:27       ` Theodore Tso
2008-12-24  6:11         ` Masami Hiramatsu
2009-01-10  2:48           ` Theodore Tso
2009-01-11 16:29             ` Frank Ch. Eigler
2009-01-12 18:18               ` Masami Hiramatsu
2009-01-12 18:53                 ` Frank Ch. Eigler
2009-01-12 19:29                   ` Masami Hiramatsu
2009-01-12 19:26               ` Theodore Tso
2009-01-12 20:01                 ` Frank Ch. Eigler
2009-01-12 19:05             ` Jason Baron
2009-01-12 19:52               ` Theodore Tso
2009-01-12 20:32                 ` Frank Ch. Eigler
2009-01-08  9:22         ` Roland McGrath
2009-01-10  1:33           ` Theodore Tso
2008-12-22 23:34   ` Masami Hiramatsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=494BFBBF.3090804@redhat.com \
    --to=wcohen@redhat.com \
    --cc=fche@redhat.com \
    --cc=hisashi.hashimoto.wh@hitachi.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=mhiramat@redhat.com \
    --cc=satoshi.oshima.fk@hitachi.com \
    --cc=systemtap@sourceware.org \
    --cc=yumiko.sugita.yf@hitachi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).