Bug 1606

Summary: interrupted system
Product: frysk Reporter: Andrew Cagney <cagney>
Component: generalAssignee: Jeff Johnston <jjohnstn>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P1    
Version: unspecified   
Target Milestone: ---   
Host: Target:
Build: Last reconfirmed:
Bug Depends on:    
Bug Blocks: 1524    

Description Andrew Cagney 2005-10-29 03:03:25 UTC 
need to determine (kernel doco, yea right), and test a system call being
interrupted - is there always sysenter and sysexit; or sysenter and syscall?
Comment 1 Jeff Johnston 2005-11-18 23:53:01 UTC 
New test frysk.proc.TestSyscallInterrupt added which tests attaching to a
process currently in a blocked read and properly tracing syscall enter and exit.
 The test signals the process so that the read is interrupted and is performed a
2nd time allowing the read to restart.

Test runs successfully and in both cases we see sysenter / sysexit pairs
properly determined by TaskState transitions.