Bug 1606 - interrupted system
Summary: interrupted system
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Jeff Johnston
URL:
Keywords:
Depends on:
Blocks: 1524
  Show dependency tree / graph
 
Reported: 2005-10-29 03:03 UTC by Andrew Cagney
Modified: 2005-11-18 23:53 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 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.