Bug 2736 - Multiple Frysk processes acccessing same Druid session object = Exception
Summary: Multiple Frysk processes acccessing same Druid session object = Exception
Status: RESOLVED DUPLICATE of bug 2619
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Andrew Cagney
Depends on:
Reported: 2006-06-08 20:51 UTC by Len DiMaggio
Modified: 2006-06-15 15:55 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 Len DiMaggio 2006-06-08 20:51:54 UTC
Multiple Frysk processes acccessing same Druid session object = Exception

Are we planning on restricting a user to running one Frysk session at a time on
a system? Or, are we planning on having the GUI prevent multiple Frysk sessions
to access the same Session object?

We need to do one or the other of these - right now, if a second Frysk session
starts up and tries to access a session object that is in use - this exception

Frysk Core has reported the following errors


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 Stan Cox 2006-06-14 15:18:26 UTC
Just did a quick experiment and this seems to work now.
If ptrace was failing with EPERM then this is being caught now (#2619)
Comment 2 Phil Muldoon 2006-06-15 02:34:44 UTC
This is not so much to do with sessions, but the fact that using ptrace only one
process can attach to a process. So the the second frysk instance using the same
session object is trying to attach to a process that is already attached to. I'm
not sure how to fix this other than creating .lock files. Any comments to this
Comment 3 Andrew Cagney 2006-06-15 15:55:34 UTC

*** This bug has been marked as a duplicate of 2619 ***