Bug 3473 - TestLib.Child.sendStopXXX aka assertSendStop doesn't
Summary: TestLib.Child.sendStopXXX aka assertSendStop doesn't
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Nurdin Premji
URL:
Keywords:
Depends on:
Blocks: 2235 3316
  Show dependency tree / graph
 
Reported: 2006-11-07 15:33 UTC by Andrew Cagney
Modified: 2007-01-12 20:00 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-11-07 15:33:49 UTC 
The method TestLib.Child.sendStopXXX doesn't check that the STOP signal was
delivered (which is why it was re-named from assertSendStop - having assert in
the name does imply that it asserts something!).

The method needs to, somehow or other confirm signal delivery as otherwize
there's a race between sending that signal and any follow-on testing relying on
the signal being delivered.

Also, I assume this only works on detached threads.
Comment 1 Nurdin Premji 2007-01-12 20:00:27 UTC 
Fixed.
January 12, 2007
frysk-core/frysk/proc/CL
	* TestProcStopped.java (stopped): Updated name change from sendStopXXX 
	to assertSendStop.
	* TestLib.java (AckProcess.assertSendStop): Renamed from sendStopXXX. Now
	ensures that the process is in state 'T'. Bug #3473