From: "Frank Ch. Eigler" <fche@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ksummit-2008-discuss@lists.linux-foundation.org,
systemtap@sources.redhat.com
Subject: Re: [Ksummit-2008-discuss] DTrace
Date: Mon, 30 Jun 2008 22:10:00 -0000 [thread overview]
Message-ID: <20080630204219.GA6631@redhat.com> (raw)
In-Reply-To: <20080630201031.GF7988@mit.edu>
Hi -
On Mon, Jun 30, 2008 at 04:10:31PM -0400, Theodore Tso wrote:
> [...]
> > They shouldn't have to repackage it at all - just leave it in the
> > build tree.
>
> The problem is that I am often juggling multiple kernel builds, and so
> I don't want to keep the full build tree around. So I just want to
> extract out the specific files needed by Systemtap [...]
OK, we'll have to think about how to support that well.
> Stupid question --- has anyone thought about writing tools to strip
> out specific debug information not needed by Systemtap?
Yes, but nothing so simple/workable as to have been done already.
> For example, I assume systemtap doesn't need the line number
> information, since you can't set probes on arbitrary line numbers
Actually, we can - and now with wildcards too if you want
source-line-by-line tracing. See the top of the NEWS file.
> (and even if you could, such tapsets would be so brittle that it
> wouldn't be funny); [...]
Yes, this is not a good fit for tapsets, but is handy for exploring
one's known version of code. Also, we can now use relative line
numbers (line #10 within this function), which might be stable enough
for some tapset use. (This is all very recent stuff, beware.)
> [...] What about stripping out the text segment of the object
> files, so you aren't storing the information twice on disk, or
> compressing the debuginfo files so they take up less room on disk?
This is roughly what the Fedora/RHEL-style separated .ko.debug files
do, though I don't know if they are that complete. (They'd need a
copy of the symbol tables, and probably other stuff.)
- FChE
next prev parent reply other threads:[~2008-06-30 20:44 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 13:57 DTrace Frank Ch. Eigler
2008-06-30 19:00 ` [Ksummit-2008-discuss] DTrace Grant Grundler
2008-06-30 19:40 ` Theodore Tso
2008-06-30 20:00 ` Frank Ch. Eigler
2008-06-30 20:19 ` Theodore Tso
2008-06-30 21:12 ` Arnaldo Carvalho de Melo
2008-06-30 23:02 ` David Miller
2008-06-30 21:13 ` James Bottomley
2008-06-30 22:10 ` Frank Ch. Eigler [this message]
2008-07-01 2:42 ` Theodore Tso
2008-07-01 7:08 ` Roland McGrath
2008-07-01 10:15 ` Theodore Tso
2008-07-01 11:04 ` Sam Ravnborg
2008-07-01 12:13 ` Theodore Tso
2008-07-02 20:27 ` Sam Ravnborg
2008-07-01 20:06 ` Roland McGrath
2008-07-01 23:13 ` Theodore Tso
2008-07-02 2:23 ` Frank Ch. Eigler
2008-07-02 19:27 ` Frank Ch. Eigler
2008-07-02 21:40 ` Potential Systemtap topics for the Kernel Summit Theodore Tso
2008-07-02 21:51 ` [Ksummit-2008-discuss] " Jonathan Corbet
2008-07-02 23:41 ` Arnaldo Carvalho de Melo
2008-07-02 22:38 ` Masami Hiramatsu
2008-07-02 22:54 ` [Ksummit-2008-discuss] " Stephen Hemminger
2008-07-03 0:44 ` Ulrich Drepper
2008-07-03 1:02 ` H. Peter Anvin
2008-07-03 1:50 ` Theodore Tso
2008-07-03 1:51 ` Ulrich Drepper
2008-07-02 20:08 ` [Ksummit-2008-discuss] DTrace Joel Becker
2008-07-02 20:17 ` J. Bruce Fields
2008-07-02 20:41 ` Frank Ch. Eigler
2008-07-02 21:19 ` H. Peter Anvin
2008-07-02 21:30 ` Theodore Tso
2008-07-02 21:46 ` J. Bruce Fields
2008-07-05 9:46 ` Peter Zijlstra
2008-07-05 10:07 ` Christoph Hellwig
2008-07-05 12:12 ` Frank Ch. Eigler
2008-07-05 18:08 ` Christoph Hellwig
2008-07-05 13:50 ` James Bottomley
2008-07-05 18:08 ` Christoph Hellwig
2008-07-05 18:05 ` K.Prasad
2008-07-07 14:36 ` Christoph Hellwig
2008-07-07 17:44 ` K.Prasad
2008-07-05 12:34 ` Theodore Tso
2008-07-01 5:29 ` Ananth N Mavinakayanahalli
2008-06-30 19:59 ` James Bottomley
2008-06-30 23:52 ` Masami Hiramatsu
2008-07-08 23:32 ` Eric W. Biederman
[not found] <20080627150424.GB14894@parisc-linux.org>
[not found] ` <1214580213.3394.40.camel@localhost.localdomain>
[not found] ` <20080627155018.GC14894@parisc-linux.org>
[not found] ` <1214583502.7698.15.camel@weaponx>
[not found] ` <20080627163056.GB1416@lst.de>
[not found] ` <20080628072605.GA505@in.ibm.com>
[not found] ` <20080629084002.GA24131@lst.de>
[not found] ` <20080630051034.GA4970@in.ibm.com>
[not found] ` <20080630112913.GA18817@lst.de>
2008-06-30 19:27 ` Frank Ch. Eigler
2008-07-01 1:21 ` Jim Keniston
[not found] ` <20080706123414.GA9265@lst.de>
2008-07-06 15:47 ` Frank Ch. Eigler
2008-07-06 16:36 ` Evgeniy Polyakov
2008-07-06 18:05 ` Frank Ch. Eigler
2008-07-06 18:24 ` Evgeniy Polyakov
2008-07-06 21:46 ` Frank Ch. Eigler
2008-07-06 22:47 ` Karen Shaeffer
2008-07-06 23:15 ` Frank Ch. Eigler
2008-07-07 5:59 ` Evgeniy Polyakov
2008-07-07 11:19 ` Frank Ch. Eigler
[not found] ` <20080627182754.GB7549@mit.edu>
[not found] ` <1214597135.3394.82.camel@localhost.localdomain>
[not found] ` <aday74qlh08.fsf@cisco.com>
[not found] ` <4865B111.2040307@redhat.com>
[not found] ` <adavdzujh2u.fsf@cisco.com>
[not found] ` <20080704200055.GA11232@synapse.neuralscape.com>
[not found] ` <20080704224424.GA12454@synapse.neuralscape.com>
[not found] ` <1215273663.3439.34.camel@localhost.localdomain>
2008-07-06 23:33 ` Frank Ch. Eigler
2008-07-07 14:35 ` James Bottomley
2008-07-07 15:02 ` James Bottomley
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=20080630204219.GA6631@redhat.com \
--to=fche@redhat.com \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--cc=systemtap@sources.redhat.com \
--cc=tytso@mit.edu \
/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).