From: Peter Bach <peterzbach@comcast.net>
To: Mike Mason <mmlnx@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: SystemTap on Ubuntu 7.04 i386
Date: Thu, 07 Jun 2007 13:21:00 -0000 [thread overview]
Message-ID: <46680618.4010705@comcast.net> (raw)
In-Reply-To: <46659C45.9010309@us.ibm.com>
Mike Mason 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.
This is a great idea, to have the debuginfo available. The situation I
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. I always take the defaults for a kernel
build, I want to use a computer for useful stuff; I would hate to
calculate how much time I've wasted compiling kernels just to get
debuginfo for SystemTap. Is there a better way?
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 that impedes that
uptake of SystemTap for all but die hard users.
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.
next prev parent reply other threads:[~2007-06-07 13:21 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 [this message]
2007-06-07 14:51 ` Frank Ch. Eigler
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=46680618.4010705@comcast.net \
--to=peterzbach@comcast.net \
--cc=mmlnx@us.ibm.com \
--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).