From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/14711] New: Support stapdyn for --remote execution
Date: Thu, 11 Oct 2012 19:57:00 -0000 [thread overview]
Message-ID: <bug-14711-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14711
Bug #: 14711
Summary: Support stapdyn for --remote execution
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
We should enhance the --remote option to work with stapdyn too. This will need
a few things, like querying whether the remote even has dyninst, and modifying
or replacing stapsh's "run" command with something new to invoke stapdyn.
We currently fork systemtap_session for kernel/arch differences. The arch will
still matter here, of course, but the kernel really doesn't. It may not matter
much though whether we bother to avoid forking remotes with different kernels.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-10-11 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 19:57 jistone at redhat dot com [this message]
2024-03-14 23:45 ` [Bug dyninst/14711] " 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=bug-14711-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).