From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-bugzilla-return-3291-listarch-frysk-bugzilla=sourceware.org@sourceware.org>
Received: (qmail 21217 invoked by alias); 6 Feb 2008 10:51:48 -0000
Received: (qmail 21121 invoked by uid 48); 6 Feb 2008 10:51:01 -0000
Date: Wed, 06 Feb 2008 10:51:00 -0000
Message-ID: <20080206105101.21120.qmail@sourceware.org>
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
In-Reply-To: <20080206091611.5735.pmuldoon@redhat.com>
References: <20080206091611.5735.pmuldoon@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/5735] testCoreThenRunCommand(frysk.hpd.TestCoreCommand) test fails
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: 2008-q1/txt/msg00289.txt.bz2
List-Id: <frysk-bugzilla.sourceware.org>


------- Additional Comments From pmuldoon at redhat dot com  2008-02-06 10:51 -------
Removing the injection of this message from frysk.step.SteppingEngine in
updateTerminating:

	    tse.setState(new StepTerminatedState(task, true));
	    if (signal != null)
		tse.setMessage(tse.getMessage()
			       + "Task " + task.getTid()
			       + " is terminating from signal " + signal);
	    else
		tse.setMessage(tse.getMessage()
			       + "Task " + task.getTid()
			       + " is exiting with status " + value);

	    steppingObserver.notifyNotBlocked(tse);

and the test passes. Looking at why, through the eventual change of execution:

Inside frysk/hpd/CLI.java, in the class SteppingObserver we see:

       public void update (Observable observable, Object arg) {
            TaskStepEngine tse = (TaskStepEngine) arg;
            if (!tse.isAlive()) {
		addMessage(tse.getMessage(), Message.TYPE_VERBOSE);
		tse.setMessage("");
		flushMessages();

If another message (say from the run command) alters the output of the message
buffer during flush, the concurrent exception error seems to happen.

-- 


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

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