[Bug translator/10822] procfs file created too late

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From dsmith at redhat dot com  2009-10-22 13:26 -------
(In reply to comment #3)
> (In reply to comment #1)
> > While we are in our initialization phase, any probes that fire will quietly skip
> > their handlers.  We have a guarantee that begin probes will fire before any
> > others, so we can't run a procfs handler before then.  If you changed the
> > initialization order, then you might get your procfs file created sooner, but
> > reads/writes to it might be ignored.
> 
> I don't want to run any procfs probes, I just want to setup the procfs file.  If
> a procfs read/write happened before systemtap got fully initialized, it should
> get skipped (just as with any other probe type).
> 
> Think of creating the procfs file as no different than registering a kprobe.

After looking at the code a bit more, I think I was looking at this incorrectly.
 kprobes are registered after any begin probes are run.  So, the initialization
order appears correct.

This is really a testcase problem.


-- 


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.