public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Frank Eigler <fche@redhat.com>
To: "Discussion list for crash utility usage,
	maintenance and development" <crash-utility@redhat.com>
Cc: systemtap@sources.redhat.com, yumiko.sugita.yf@hitachi.com
Subject: Re: [RFC] Crash extension for SystemTap
Date: Wed, 23 May 2007 19:01:00 -0000	[thread overview]
Message-ID: <y0mk5uztle4.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <46542938.3070502@hitachi.com>


Satoru MORIYA <satoru.moriya.br@hitachi.com> writes:

> [...]
> (A) Build the shared-object(stplog.so).
> 1. Put Makefile and stplog.c into a directory ($DIR)
>     $ cd $DIR
> 2. Make the symbolic link to the crash source code directory
>     $ ln -s $WHERE_CRASH_PLACED crash

It would be nice if crash(8) had a -devel package against which such
an extension could be built.  I submitted RH bug #241045 to try to fix
this.  If that is done, we can include the stplog sources in systemtap,
and build a .so as a part of our build.

> [...]  I believe this command is very useful for system
> administrators if they monitor their systems with SystemTap.

Indeed!  Thank you.


- FChE

  parent reply	other threads:[~2007-05-23 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 11:46 Satoru MORIYA
2007-05-23 13:22 ` [Crash-utility] " Dave Anderson
2007-05-23 19:01 ` Frank Eigler [this message]
2007-05-24  0:54 ` Satoru MORIYA
2007-05-24 14:44   ` [Crash-utility] " Dave Anderson
2007-06-22 13:43     ` Satoru MORIYA
2007-06-25 16:55       ` Frank Ch. Eigler
2007-07-02 19:48       ` Frank Ch. Eigler
2007-08-20 13:42         ` [Crash-utility] " Satoru MORIYA
2007-08-20 17:50           ` 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=y0mk5uztle4.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=crash-utility@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --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).