Bug 2619 - Can't add an observer to init (PID = 1)
Summary: Can't add an observer to init (PID = 1)
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
: 2586 2736 (view as bug list)
Depends on:
Blocks: 1553
  Show dependency treegraph
 
Reported: 2006-04-28 14:17 UTC by Len DiMaggio
Modified: 2007-03-19 13:17 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
2619 patch (932 bytes, patch)
2006-06-13 14:36 UTC, Stan Cox
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Len DiMaggio 2006-04-28 14:17:25 UTC
Can't add an observer to init (PID = 1)

I'm, wondering if the null value is related to Frysk looking for init's parent
process?

The error displayed is:

=================================
Frysk Core has reported the following errors

null

frysk.proc.LinuxTask.sendAttach (FryskGui)
frysk.proc.TaskState$1.handleAttach (FryskGui)
frysk.proc.Task.performAttach (FryskGui)
frysk.proc.ProcState$Attaching.initialState (FryskGui)
frysk.proc.ProcState$1.handleAddObservation (FryskGui)
frysk.proc.Proc.handleAddObservation (FryskGui)
frysk.proc.Proc$6.execute (FryskGui)
frysk.event.EventLoop.runEventLoop (FryskGui)
frysk.event.EventLoop.run (FryskGui)
frysk.gui.Gui$3.run (FryskGui)
java.lang.Thread.run (libgcj.so.7)
Comment 1 Len DiMaggio 2006-04-28 14:28:36 UTC
Actually - it's failing for most processes - this bug may be premature as the
GUI may not be ready for real testing yet.
Comment 2 Andrew Cagney 2006-05-12 19:29:40 UTC
Not allowed to attach to PID 1, need better error recovery when permission
denied - should notify GUI of failure rather than panic (all the hooks are ready).

Comment 3 Andrew Cagney 2006-05-30 06:47:02 UTC
*** Bug 2586 has been marked as a duplicate of this bug. ***
Comment 4 Stan Cox 2006-06-12 16:43:18 UTC
With the current state of the druid there is no longer an obvious way to trigger
or test this since the druid only lists processes you own, and thus doesn't list
process init.
Comment 5 Stan Cox 2006-06-13 14:36:18 UTC
Created attachment 1083 [details]
2619 patch
Comment 6 Stan Cox 2006-06-13 14:40:04 UTC
Running frysk-gui as root still exhibits this problem.  This patch fixes it by
adding EPERM and then catching it in FryskGui.
Comment 7 Stan Cox 2006-06-14 02:35:12 UTC
* LinuxTask.java (sendAttach):  Handle Errno.Eperm.
* Errno.java (Eperm): New.
* cni/Errno.cxx (throwErrno): Added EPERM.
Comment 8 Andrew Cagney 2006-06-15 15:49:42 UTC
FYI, the core needs to handle this exception locally.
Comment 9 Andrew Cagney 2006-06-15 15:55:34 UTC
*** Bug 2736 has been marked as a duplicate of this bug. ***
Comment 10 Len DiMaggio 2006-06-23 18:21:15 UTC
FYI - this bug is still present in Frysk as built from CVS head on June 21.
Comment 11 Len DiMaggio 2006-06-23 18:28:48 UTC
Correction - what I meant to say was that if Frysk is run as root, the init
process still appears in the gui and can have observers attached to it.
Comment 12 Phil Muldoon 2006-11-28 15:37:37 UTC
As of the RHEL5 latest rpm, the init process should not be in the druid as there
are filters in place to exclude it. Additionally, no process wil be shown that
does not match Manager.UID/GID == Process.UID/GID