From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/5892] New: support "stap -r KERNEL-BUILD-TREE"
Date: Thu, 06 Mar 2008 20:59:00 -0000 [thread overview]
Message-ID: <20080306205837.5892.fche@redhat.com> (raw)
There's a need to allow users who build their own kernels in oddball directories
to sic systemtap at them. This may go beyond $SYSTEMTAP_DEBUGINFO_PATH.
While at it, we could drop the "-r REV implies -p4" heuristic, as someone
attempting to run a crosscompiled module will get a failure message pretty
soon anyway.
--
Summary: support "stap -r KERNEL-BUILD-TREE"
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5892
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-03-06 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 20:59 fche at redhat dot com [this message]
2008-09-29 23:52 ` [Bug translator/5892] " fche at redhat dot com
2008-09-29 23:53 ` fche at redhat dot com
2008-10-03 15:07 ` fche at redhat dot com
2008-11-05 20:21 ` [Bug translator/5892] support stap against plain KERNEL-BUILD-TREE fche at redhat dot com
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=20080306205837.5892.fche@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--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).