Bug 2285 - Adding an observer for the frysk app hangs the application
Summary: Adding an observer for the frysk app hangs the application
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Phil Muldoon
Depends on:
Blocks: 1582 2004
  Show dependency treegraph
Reported: 2006-02-06 20:46 UTC by Andrew Cagney
Modified: 2006-11-28 15:11 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-02-06 20:46:55 UTC
From: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179874

Description of problem:

Of course you shouldn't do this, but if you try to add an observer to frysk, it
hangs.  I get this on the terminal:

click : frysk.gui.monitor.ProcData@4e0f110
Exception in thread "Thread-2" ptrace.attach: Operation not permitted (process 6707)
   at java.lang.Exception.Exception() (/usr/lib/libgcj.so.6.0.0)
   at java.lang.RuntimeException.RuntimeException() (/usr/lib/libgcj.so.6.0.0)
   at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0)

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1.  Install frsyk
2.  as a user, sudo frysk
3.  add any observer for the frysk process
Actual results:
frysk hangs

Expected results:
the observer is not added, but the app continues to run (maybe displays a warning?)

Additional info:
Comment 1 Phil Muldoon 2006-02-21 21:36:41 UTC
This may have been fixed in the RHEL4-U3 update (and therefore in head). There
was an error in the way we were associating parents in the treeview. Can you
retest and report?
Comment 2 Phil Muldoon 2006-11-28 15:11:24 UTC
In addition, the user is now not allowed to attach to the *same* frysk process
that the user is interacting with, but only other ancillary and incidental frysk
processes running on the system. Closing, as OP did not reply, and this bug has
been not been seen, and potentially cannot happen with the code changes past OP