public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Roland McGrath <roland@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: nits to please a kernel hacker
Date: Tue, 30 Sep 2008 13:55:00 -0000	[thread overview]
Message-ID: <20080930135504.GN10831@mit.edu> (raw)
In-Reply-To: <20080929230107.18F95154253@magilla.localdomain>

On Mon, Sep 29, 2008 at 04:01:07PM -0700, Roland McGrath wrote:
> 	sh: /usr/local/bin/staprun: No such file or directory
> 	Pass 5: run completed in 0usr/10sys/11real ms.
> 	Pass 5: run failed.  Try again with more '-v' (verbose) options.
> 	Running rm -rf /tmp/stapXpCOU6
> 	-bash-3.2$ 
> 
> Ok, there is finally.  Two -v's just to see the command line it tried to run?
> Really?  Even though you deserved it for that smarmy damn error message,
> I'm feeling a little bad about the tire-iron.  So, I'm working with ya!

Note that run stap, "try again with more '-v'", rinse, repeat loop is
really annoying not just to kernel developers, but also to System
Administrators.  (Especially ones that were dragged kicking and
screaming to Linux and are longing for Dtrace.)

Stupid question, is there a reason than messages from stderr are
filtered out unless a sufficiently high -v is given?  I can see
wanting to filter out warning messages, but are there normally lots of
error messages sent out to stderr that need to be filtered?

Here's a potentially stupid suggestion --- why not pipe stdout and
stderr into a perl script which is resposible for doing the filtering?
With a perl script it might be possible to do more intelligent
filtering based on regexp's and then translate some very
unintelligible error messages from the compiler, linker, or whatever
into more user-friendly error messages.

						- Ted

  parent reply	other threads:[~2008-09-30 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 23:02 Roland McGrath
2008-09-30 11:28 ` Srikar Dronamraju
2008-09-30 13:55 ` Theodore Tso [this message]
2008-09-30 14:11   ` Frank Ch. Eigler
2008-09-30 16:24     ` Theodore Tso
2008-09-30 17:09       ` Frank Ch. Eigler
2008-09-30 17:33         ` Theodore Tso
2008-09-30 18:57           ` Frank Ch. Eigler

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=20080930135504.GN10831@mit.edu \
    --to=tytso@mit.edu \
    --cc=roland@redhat.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).