This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/5735] testCoreThenRunCommand(frysk.hpd.TestCoreCommand) test fails
- From: "pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 6 Feb 2008 10:38:44 -0000
- Subject: [Bug general/5735] testCoreThenRunCommand(frysk.hpd.TestCoreCommand) test fails
- References: <20080206091611.5735.pmuldoon@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pmuldoon at redhat dot com 2008-02-06 10:38 -------
Altering the test has no effect. However I was investigating the cause of EOF.
Adding in a System.out.println into frysk.expunit.Child and the function:
expectMilliseconds:
System.out.print("Expect output: " + output);
if (eof) {
fine.log(this, "match EOF");
throw new EndOfFileException(matches, output);
}
I get the output:
Expect output: run
Attached to process 11658
starting/running with this command:
/home/pmuldoon/frysk_bin/frysk-core/frysk/pkglibdir/funit-hello
Exception in thread "main" starting/running with this command:
/home/pmuldoon/frysk_bin/frysk-core/frysk/pkglibdir/funit-hello
java.util.ConcurrentModificationException
at java.util.LinkedList$LinkedListItr.checkMod(libgcj.so.8rh)
at java.util.LinkedList$LinkedListItr.remove(libgcj.so.8rh)
at frysk.hpd.CLI.flushMessages(fhpd)
at frysk.hpd.CLI.execCommand(fhpd)
at frysk.bindir.fhpd.main(fhpd)
FAIL
junit.framework.AssertionFailedError: sent: <run > expecting: <Attached to
process ([0-9]+).*Running process ([0-9]+).*> got: <EOF>
Looking at flushmessages() in CLI.java:
private void flushMessages() {
for (Iterator iter = messages.iterator(); iter.hasNext();) {
I see the use of a fail-fast iterator. I suspect that in the SteppingEngine, the
injection of:
Task 10858 is terminating from signal SIGSEGV(11)
Is causing a concurrent modification exception and causing an EOF
--
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.