From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-bugzilla-return-1712-listarch-frysk-bugzilla=sourceware.org@sourceware.org>
Received: (qmail 31607 invoked by alias); 28 Mar 2007 08:55:55 -0000
Received: (qmail 31570 invoked by uid 48); 28 Mar 2007 08:55:40 -0000
Date: Wed, 28 Mar 2007 08:55:00 -0000
Message-ID: <20070328085540.31569.qmail@sourceware.org>
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
In-Reply-To: <20070308215939.4174.mcvet@redhat.com>
References: <20070308215939.4174.mcvet@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/4174] Frysk blows up with heavily threading programs.
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:frysk-bugzilla-subscribe@sourceware.org>
List-Post: <mailto:frysk-bugzilla@sourceware.org>
List-Help: <mailto:frysk-bugzilla-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: frysk-bugzilla-owner@sourceware.org
X-SW-Source: 2007-q1/txt/msg00860.txt.bz2
List-Id: <frysk-bugzilla.sourceware.org>


------- Additional Comments From mark at klomp dot org  2007-03-28 09:55 -------
The problem here is that frysk.rt.RunState throws a hissy fit when it sees any
addObservation failing:

  public void addFailed (Object o, Throwable w)
  {
    w.printStackTrace();
    stateProc.requestAbandonAndRunEvent(new RequestStopEvent(Manager.eventLoop)\
);
    System.exit(1);
  }

The TaskState really cannot help that the request for an observer addition was
done just at the moment the Task was about to be destroyed.

Is there anything the TaskState can do to help RunState recover in this case?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4174

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.