This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/6525] need utrace task-finder-based pid->execname, pid->cwd-path-name tables
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 04 Aug 2014 16:20:20 +0000
- Subject: [Bug tapsets/6525] need utrace task-finder-based pid->execname, pid->cwd-path-name tables
- Auto-submitted: auto-generated
- References: <bug-6525-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=6525
--- Comment #13 from David Smith <dsmith at redhat dot com> ---
(In reply to Frank Ch. Eigler from comment #12)
> David, I think the old idea was to introduce some tapset functions that,
> based on kprocess.* probes or the like, maintain global data like pid2FOO
> tables for use by stap. The idea was not to -read- /proc/$PID/foo, but to
> track some equivalent data within stap globals.
Yes, that was the old idea. I thought Martin was proposing a new idea of
reading /proc/$PID/foo.
With enough work, we could probably maintain some global data that mapped pids
to execnames. The unfortunate part would be that it would have to map every
single process in the system in order to be able to give you any pid.
Mapping pids to cwd paths would be harder, since we don't keep up with that
now.
The trickiest part of all of this would be finding storage for all this new
information, especially paths.
--
You are receiving this mail because:
You are the assignee for the bug.