From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/4917] New: permit on-the-fly program/module symbol data transfer
Date: Mon, 13 Aug 2007 18:25:00 -0000 [thread overview]
Message-ID: <20070813163047.4917.fche@redhat.com> (raw)
The fix for bug #4916 makes it harder to enable the system to support
dynamically updated module/symbol data.
The scenarios involve probes on libraries or modules that are not yet loaded,
and thus whose addresses cannot be sent to the module at initialization time.
If there was a secure channel available to staprun (and if staprun stayed
running, even if stapio was suspended), then staprun could inform the module
that there was more probe target code coming online.
Another scenario is probing a user program, but having the module anticipate
needing a backtrace for everything - including some libraries not yet loaded.
That library address data would have to be transmitted to the probe well
after initialization.
--
Summary: permit on-the-fly program/module symbol data transfer
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=4917
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-08-13 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 18:25 fche at redhat dot com [this message]
2007-10-10 14:08 ` [Bug runtime/4917] " mhiramat at redhat dot com
2008-01-29 21:26 ` fche at redhat dot com
2008-01-29 21:43 ` hunt at redhat dot com
2008-01-29 21:44 ` hunt 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=20070813163047.4917.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).