Bug 3193 - testSyscallRunning(frysk.proc.TestSyscallRunning)junit.framework.AssertionFailedError: syso exited
Summary: testSyscallRunning(frysk.proc.TestSyscallRunning)junit.framework.AssertionFai...
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Mark Wielaard
URL:
Keywords:
Depends on:
Blocks: 1582
  Show dependency tree / graph
 
Reported: 2006-09-11 18:21 UTC by Andrew Cagney
Modified: 2006-09-18 10:43 UTC (History)
0 users

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

Attachments
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-09-11 18:21:56 UTC 
cagney@nettle$ cd frysk-core/
cagney@nettle$ ./TestRunner -r 100 frysk.proc.TestSyscallRunning
[...]
1)
testSyscallRunning(frysk.proc.TestSyscallRunning)junit.framework.AssertionFailedError:
syso exited
   at frysk.proc.TestSyscallRunning.testSyscallRunning(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)

this is on fc5, both i386 and x86-64.
Comment 1 Mark Wielaard 2006-09-18 10:43:35 UTC 
Fixed by:

2006-09-18  Mark Wielaard  <mark@klomp.org>

     Fixes bug #3193
     * TestSyscallRunning (SyscallObserver): Take syscall name and
     whether the syscall is in an entered state. Use Syscall.getByName()
     for accept.

2006-09-18  Mark Wielaard  <mark@klomp.org>

     * funit-syscall-running.c: Don't read, just accept socket.