From: fche@redhat.com (Frank Ch. Eigler)
To: Peter Bach <peterzbach@comcast.net>
Cc: Mike Mason <mmlnx@us.ibm.com>, SystemTAP <systemtap@sources.redhat.com>
Subject: Re: SystemTap on Ubuntu 7.04 i386
Date: Thu, 07 Jun 2007 14:51:00 -0000 [thread overview]
Message-ID: <y0msl937r8a.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <46680618.4010705@comcast.net>
Peter Bach wrote:
> [...]
> > I'm wondering if we could get the distros to install the
> > vmlinux-only debuginfo by default. I'm guessing this would allow
> > 95% of systemtap to work out-of-box.
Maybe. Of the examples, tapsets, and test cases in the source tree,
only a few dozen refer to modules. Some of them are important: NFS,
SCSI.
> This is a great idea, to have the debuginfo available. The situation
> Innn find myself in is to load the distro (usually RedHat or SuSE),
> and use online repositories to keep up to date. The problem is that
> if a new kernel gets installed, I have to recompile with debuginfo
> just to get the usefulness of SystemTap.
Red Hat (RHEL and Fedora) each publish kernel-debuginfo RPMs for
downloading. yum can get 'em for you. Some distributions toss it
away during the build (Debian, Ubuntu), so those need policy changes.
> I don't know if this is a function of having the distros compile a
> version with debuginfo, or just making it available in the online
> repositories, but this would seem to be a big hurdle [...]
We have mentioned the possibility of creating a network server for
debugging information processing. The idea has not yet been fleshed
out though.
> The real value is that SystemTap is not only useful for solving
> problems in during the development cycle, but illuminates how Linux
> works under the covers, in the most dynamic way, when it is actually
> running. This is much more useful that perusing the code. The target
> audience for this is only every CS student on the planet.
Yeah - mind if I quote you on that? ;-)
- FChE
next prev parent reply other threads:[~2007-06-07 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 17:24 Mike Mason
2007-06-05 18:23 ` Mike Mason
2007-06-07 13:21 ` Peter Bach
2007-06-07 14:51 ` Frank Ch. Eigler [this message]
2007-06-07 23:59 ` darrell pfeifer
2007-06-08 0:15 ` Vara Prasad
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=y0msl937r8a.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=mmlnx@us.ibm.com \
--cc=peterzbach@comcast.net \
--cc=systemtap@sources.redhat.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).