This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/10822] New: procfs file created too late
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 21 Oct 2009 21:10:07 -0000
- Subject: [Bug translator/10822] New: procfs file created too late
- Reply-to: sourceware-bugzilla at sourceware dot org
I've investigated some testsuite/systemtap.base/onoffprobe.exp failures I was
seeing. After seeing the output from the begin probe, the testcase immediately
tries to write to the procfs file created by the script. This kept failing.
In looking at the translator-created C file, I see this:
====
for (i=0; i<2; i++) {
struct stap_be_probe* stp = & stap_be_probes [i];
if (stp->type == 1)
enter_be_probe (stp);
}
for (i=0; i<2; i++) {
struct stap_be_probe* stp = & stap_be_probes [i];
if (stp->type == 2)
enter_be_probe (stp);
}
goto out;
}
for (i = 0; i < 1; i++) {
struct stap_procfs_probe *spp = &stap_procfs_probes[i];
if (spp->read_pp)
probe_point = spp->read_pp;
else
probe_point = spp->write_pp;
rc = _stp_create_procfs(spp->path, i);
====
>From the above, it appears that the begin probes are run, then the procfs file
is created. I don't believe this is correct - begin probes should be run after
all the other probes types module init code has been run.
--
Summary: procfs file created too late
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: dsmith at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10822
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.