Bug 3114 - starting a spanking new session does not lead to monitored processors
Summary: starting a spanking new session does not lead to monitored processors
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 1632
  Show dependency tree / graph
 
Reported: 2006-08-23 19:29 UTC by Andrew Cagney
Modified: 2006-10-19 17:46 UTC (History)
0 users

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

Attachments
Screenshot (43.50 KB, image/png)
2006-08-23 19:57 UTC, Phil Muldoon 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-08-23 19:29:06 UTC 
Having created a session that is to monitor <<tcsh>>, and then opened it, I see
no tcsh processeses.  Ditto for a <<loop>> process that was also marked for
monitorong.
Comment 1 Andrew Cagney 2006-08-23 19:41:26 UTC 
Reproduce with:

-> rm -rf ~/.frysk

-> in a bash terminal, type tcsh (to get a unique terminal process)

-> start frysk

-> create a new session to observe fork's being done by tcsh

-> start session

no sign of tcsh
Comment 2 Phil Muldoon 2006-08-23 19:57:02 UTC 
Created attachment 1244 [details]
Screenshot
Comment 3 Mike Cvet 2006-08-23 20:02:01 UTC 
Reproducible when the session is selected by double-clicking the entry in the
session list rather than the OK button
Comment 4 Mike Cvet 2006-08-23 21:00:49 UTC 
2006-08-23  Mike Cvet  <mcvet@redhat.com>

	* SessionManagerGui.java (openSession): Added - opens the new Session correctly
in the
	MainWindow. Closes #3114.
	(getSessionManagementControls): Now calls openSession to open the new Session.
	(getManagerControls): Ditto.