From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Jun Koi" <junkoi2004@gmail.com>
Cc: 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: Thu, 18 Dec 2008 09:46:00 -0000 [thread overview]
Message-ID: <20081218183714.94C0.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <fdaac4d50812180136h72a9ef65jc3dc4e604c5c5d5f@mail.gmail.com>
> >> 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.
> >
> > So the way is to include, by default, debug information we need into
> > kernel binary? Yes, that solves the problem, provided that they
> > (kernel developers) accept that.
> >
>
> The downside is that the kernel binary becomes much much bigger.
No.
I agree with full DWARF information is _very_ big.
but if we want only dtrace level tracing, tracing section is less than few mega byte.
Then, I suggest to implement restrected (dtrace level) tracing feature.
only the user of using debuginfo can do full tracing.
Actually, average tracing user don't need line number proving.
next prev parent reply other threads:[~2008-12-18 9:42 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 [this message]
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
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=20081218183714.94C0.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=hisashi.hashimoto.wh@hitachi.com \
--cc=junkoi2004@gmail.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).