This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14489] New: Revamp probe metadata between modules and stapdyn
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sat, 18 Aug 2012 01:38:45 +0000
- Subject: [Bug runtime/14489] New: Revamp probe metadata between modules and stapdyn
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14489
Bug #: 14489
Summary: Revamp probe metadata between modules and stapdyn
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Blocks: 14178
Classification: Unclassified
Right now, stap is generating "struct stapdu_target" information in a special
section for stapdyn to read and parse. I'm not thrilled with the future of
having such a fixed ABI between modules and stapdyn, especially in the face of
compile-server or remote targets, where stap versions may be mismatched.
One idea is to shift this section to some self-describing textual format, which
stapdyn will read and parse. I've experimented a little with this, but it
seems rather clunky still.
Another idea suggested by fche is for stapdyn to dlopen+dlsym the module to
query it directly for its probe information. I like this idea, because we can
e.g. infer that a missing dlsym just means it's an older module. I'm currently
pursuing this further.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.