This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17393] java.exp: ERROR: Cannot attach to module control channel
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 21 Mar 2016 22:13:38 +0000
- Subject: [Bug runtime/17393] java.exp: ERROR: Cannot attach to module control channel
- Auto-submitted: auto-generated
- References: <bug-17393-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17393
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
It looks like what is going on here is that the java support code adds
synthetic begin and end probes that install and delete the java probes. When
the end probe happens, the system() function is run to delete the java probes.
Unfortunately, the control channel and relayfs file descriptors are passed down
to the child process, and if it is still running when the module tries to exit,
removing the module will fail. If the control channel is still open, you'll get
EAGAIN. If the relayfs file descriptors are still open, you'll get EBUSY.
Fixed in commit 9010bbb by making sure all file descriptors are closed when
needed and marked close-on-exec.
--
You are receiving this mail because:
You are the assignee for the bug.